While playing with .Net 2 and MasterPages is all very well, at the moment all the work is in .Net 1.1...
Most places ive worked in have used a combination of Custom Controls and one or more Base Pages to provide common functionality, while using CSS to provide a degree of customisation in terms of look and feel...
But its always been a bit cludgy, with no real visual representation of how the generated page will really appear.
Ive seen several implementations of MasterPages for .Net 1.1 including efforts from Micorosofts own ASP.Net team and Paul Wilsons enhancements to that. Most others just use a hierarchy of base pages and placeholders.
The most flexible seems to be Paul Wilsons approach where you define a single MasterPage that handles rendering of controls and text, have a UserControl that contains Regions where you define layout and CSS style, and a normal ASP.Net page that specifies the content for those Regions (which are automatically merged by the MasterPage) to handle presentation, while still allowing you to inherit from a specific BasePage that contains commmon functionality such as error logging, etc. Designers can fiddle with layout and the CSS while Developers can work on Presentation and Business logic etc.
Just wondered if anyone else has used any successful methodologies for creating genuinely flexible page layouts and common functionality with the current implementation of ASP.Net...
Most places ive worked in have used a combination of Custom Controls and one or more Base Pages to provide common functionality, while using CSS to provide a degree of customisation in terms of look and feel...
But its always been a bit cludgy, with no real visual representation of how the generated page will really appear.
Ive seen several implementations of MasterPages for .Net 1.1 including efforts from Micorosofts own ASP.Net team and Paul Wilsons enhancements to that. Most others just use a hierarchy of base pages and placeholders.
The most flexible seems to be Paul Wilsons approach where you define a single MasterPage that handles rendering of controls and text, have a UserControl that contains Regions where you define layout and CSS style, and a normal ASP.Net page that specifies the content for those Regions (which are automatically merged by the MasterPage) to handle presentation, while still allowing you to inherit from a specific BasePage that contains commmon functionality such as error logging, etc. Designers can fiddle with layout and the CSS while Developers can work on Presentation and Business logic etc.
Just wondered if anyone else has used any successful methodologies for creating genuinely flexible page layouts and common functionality with the current implementation of ASP.Net...
Comment