title: ASP.NET Templating
body: <p>We're building a text templating engine out of a custom HttpModule that replaces tags in our HTML with whole sections of text from an XML file.</p>
  
  <p>Currently the XML file is loaded into memory as a string/string Dictionary so that the lookup/replace done by the HttpModule can be performed very quickly using a regex.</p>
  
  <p>We're looking to expand the use of this though to incorperate larger and larger sections of replaced text and I'm concerned over keeping more verbose text in memory at one time as part of the Dictionary, especially as we use ASP.NET caching for many uses as well.</p>
  
  <p>Does anyone have a suggestion for a more efficient and scalable data structure/management strategy that we could use?</p>
  
  <p><b>UPDATE:</b> In response to Corbin March's great suggestion below, I don't think this is a case of us going down a 'dark road' (although I appreciate the concern). Our application is designed to be reskinned completely for different clients, right down to text anywhere on the page - including the ability to have multiple languages. The technique I've described has proven to be the most flexible way to handle this.</p>