General Page Architecture
-
Hi everybody, I trying to come up with a web page architecture that would be easiest to use/modify and I can't come up with a satisfying result. This is my idea about how the architecture should work: - there is a parent page with defined layout - header, footer, side menu, content panel (placeholder) - each child page would derive from parent page (having same header, footer, side menu) and defines it's unique content in the content panel - child design derived from parent is available in design time in VS designer I tried to use dynamic approach by having one
default.aspxwith header, footer, side menu and content panel. InInitphase content (user controls) was loaded. Problem was that I could not handle content events properly, and after some research I've realized that it's not possible in .NET 2.0 , as the event's fired by content user controls are too late to properly add and register different content on same place in one postback. I was also considering creating one parent.aspx control, but if the page design is created in design view (html), it's not passed to any children as it is obviously not a part of parent's code behind. thanx for any adviceszilo
-
Hi everybody, I trying to come up with a web page architecture that would be easiest to use/modify and I can't come up with a satisfying result. This is my idea about how the architecture should work: - there is a parent page with defined layout - header, footer, side menu, content panel (placeholder) - each child page would derive from parent page (having same header, footer, side menu) and defines it's unique content in the content panel - child design derived from parent is available in design time in VS designer I tried to use dynamic approach by having one
default.aspxwith header, footer, side menu and content panel. InInitphase content (user controls) was loaded. Problem was that I could not handle content events properly, and after some research I've realized that it's not possible in .NET 2.0 , as the event's fired by content user controls are too late to properly add and register different content on same place in one postback. I was also considering creating one parent.aspx control, but if the page design is created in design view (html), it's not passed to any children as it is obviously not a part of parent's code behind. thanx for any adviceszilo
Have you tried Master Pages[^]?
Declan Bright www.declanbright.com