Reply to thread

Message: [QUOTE="Rob R. Ainscough, post: 1570099"] Bruno, yeah, I finally got that now -- I've got it working and the big saving grace is the Master. functionality that can be used in code behind for any content page. I think documentation was severely lacking in just about every place I looked and my WROX books just restated what MSDN states. I think the key that was missed is that Master pages ARE templates, sure they have a tad more functionality, but if more time were spent saying they are "templates" then that would have triggered the concept much more clearly. It's like they didn't want to use the word "template" because master pages offer a little more than that. I think it would also have been beneficial if the rendering process were presented more clearly also -- content pages are NOT true web pages even though they have the aspx extension -- this again was completely NOT presented. Since the end result is something very similar to framesets, it would also have been more informative if that point of view were used to help the learning transition over to Master page concept -- saying "it is very different" doesn't really help. But as far as converting existing web applications -- I'm still debating whether it is worth the effort. And I'm still not sure how to get Forms authentication to work with this approach?? Not to mention how to get SSL to work correctly for parts of my site rather than the entire site. Rob. [/QUOTE]