JohnHadj
Registered: 09/13/05
Posts: 697
|
|
|
Reply with quote | #1 |
asp.net permits nested master pages. This is an extremely useful feature.
Nested master pages make it easy to have an overall layout, and then specialise it for different parts of the application.
It could be relatively easy for ISD to make this possible, the fly-out menu in Application Explorer could have an option that lists existing master pages as it does for aspx pages.
As to naming the ContentPlaceHolder, a default name derived from the page name would be OK since the content page is based on the master bage, and ISD can know the name of the ContentPlaceHolder
John
|
| |
jpatel
|
|
|
Reply with quote | #2 |
On the last point the content place holder name/id should probably remain constant and not different on each content page. Perhaps I misunderstood?
Nesting has interesting possibilities, but I don't believe there is a limitation on Designer's part.
Yes 'tooling' for nesting master pages in the designer would be nice, but I would want other master page features (like the others you mentioned) to be implemented first before this one.
Out of curiosity, does vs2008 provide any features to manage nesting in design mode? If vs2008 doesn't then likely there are some challenges with this or there wasn't enough interest from the community.... in which case Designer will not likely have it any time soon.
Importance: 4 out of 10
__________________
Get Iron Speed Designer and ASP.NET tips by rss or email |
| |
JohnHadj
Registered: 09/13/05
Posts: 697
|
|
|
Reply with quote | #3 |
I don't think that nesting is straightforward with ISD, the designer includes things in the pages that don't nest. I spent about half a day trying to get nesting to work and gave up.
VS2008 displays nested master pages correctly in the Designer page and coding is straighforward in the Source page and I've used them extensively - very useful.
For example, in my current application I have a "main" master page that has header, footer, menus, general branding, etc. I derive three other master pages from it: One for internal user pages, one for pages that are used by "managers", and another for external users. Pages for each of these categories of user are derived from the appropriate (sub-)master page. The three types of page have layouts that are appropriate to the purpose, and the aspects of the layout that are common to all are kept together.
John
|
| |
RSS(.NETCodeGenerationIsHere).gif)
