The demonstrates a nice way of implementing master pages in ASP.NET. Please see the help file MasterPages.htm in the zip file.
Works pretty well...
Reviewed by: The Spook on Friday, June 11, 2004
4 Stars
Although it does generate some funky id names. A most excellent reimplementation of this which fixes several shortcomings can be found here:
http://authors.aspalliance.com/PaulWilson/Articles/?id=14
Client Side Script
Reviewed by: felttippin on Friday, January 30, 2004
3 Stars
Yes, I have had the problem with the client side scripting because the form is renamed with the _ctrl_, but mostly because of the :. Javascript craps out when it gets to this, therefore, anything that references the form cannot be used :(
Brilliant concept, not quite intuitive
Reviewed by: craigd on Thursday, November 07, 2002
4 Stars
It took me less than 5 minutes to get the Masterpages control working in my site (just had to split the server code between what was required for the 'template' code and what was required on each page.
It was so easy, I converted a couple of pages over before I did any real testing - and then I realised my client-side script wouldn't work ! I'm definitely no .NET expert, so I had not expected all the control 'id='s to be prefixed with _ctl0__ctl0_.
I read all about INamingContainer and eventually recompiled Masterpages without it (reduced the 'id=' clutter to just _ctl0_) but not sure how safe this is (I know it won't work for repeated controls, but I'm making sure control names are unique).
If you're not worried about client-script, this is a breeze to implement!