Using nested master pages with visual design support and MasterType property set.
Posted on 2007-11-27
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?