Using nested master pages with visual design support and MasterType property set.
Hi Experts....
I am using nested master pages and have successfully used a well documented solution to workaround VS.NET 2005's lack of nested master page support in the visual designer (by setting the MasterPageFile property to an emptry string and then assigning it at runtime from a base class).
I have also successfully used the MasterType directive so that I can reference the MasterPage's properties cleanly from the content page.
What I havent been able to do is get the 2 working together, ie, if I set the MasterType directive then VS.NET understandably doesnt like the fact that MasterPageFile is an empty string (or a masterpage class different to the one specified in MasterType).
Is there any way around this?
I am using nested master pages and have successfully used a well documented solution to workaround VS.NET 2005's lack of nested master page support in the visual designer (by setting the MasterPageFile property to an emptry string and then assigning it at runtime from a base class).
I have also successfully used the MasterType directive so that I can reference the MasterPage's properties cleanly from the content page.
What I havent been able to do is get the 2 working together, ie, if I set the MasterType directive then VS.NET understandably doesnt like the fact that MasterPageFile is an empty string (or a masterpage class different to the one specified in MasterType).
Is there any way around this?
ASKER
I am looking for a solution that allows for content pages to be edited in the design view while specifying a value for MasterType. As mentioned, Design View is working already without the MasterType directive being set.
Thanks in advance.
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Although the 2008 is still in beta, it can coexist with a 2005 VS installation.
ASKER
hmmm.... downloading all 3.3 GB of the VS2008 RTM now.
I was hoping I would not have to upgrade, but I see that VS 2008 supports 2.0 framework which makes it more digestable. I'll be happy if it doesnt break anything or cause a degrade in performance.
I was hoping I would not have to upgrade, but I see that VS 2008 supports 2.0 framework which makes it more digestable. I'll be happy if it doesnt break anything or cause a degrade in performance.
I used the beta for quite a while without problems, but even if you only use it for the GUI development it can be worthwhile.
ASKER
Well upgrading did the trick in the end. Enjoying some of the other new features also.
Glad to help. Hoping to get 2008 for work soon too!
https://www.experts-exchange.com/questions/22468555/nested-master-pages.html?sfQueryTermInfo=1+master+nest+page