ASP.NET Page Templates.....

Now, which one is best? Well, I think that depends on what other things you plan to do with your pages. The techniques above vary in complexity, implementation, and how they perform in the VS.NET designer. Check out all of the techniques and let us know how they work for you by posting a comment. I'm sure we'd all love to know if you have other techniques that we should hear about (give us a comment!).

[Alex Lowe's Blog]

Alex brings up a great topic!

Here at Match, we opted to go with using standard PlaceHolders to represent different logical "slots" in a template. Then, subclassing Page into our types of specific Page implementations (session & non-session page; session subclassing non-session) which provided methods for masking how to interact with the template (eg. AddContentControl(), AddHeaderControl(), etc...).

That combined with our "template variables" (again, variables that are replaced at run-time in varying contexts), we've found it to be very very flexible.

I'll try to post more details on both our implementations of page templating and the template variables next week (this weekend is crazy, sorry!).