Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Oct 28, 2006 06:03 AM by fritz
Apr 11, 2006 06:04 PM|LINK
I have an assembly that is the core of a framework for a group of applications. The framework includes some shared base classes, some common pages, some master pages, and some controls. I am building the assembly into a single dll using a Web Deployment
I have indicated in the Web Deployment Project that all code should be built into a single assembly. That is working correctly. I have also indicated in IIS that the server should not check for the physical existence of .aspx, .ascx, and .master files.
In the code of a particular page on my site (outside of the framework project), I am setting the MasterPageFile to one of the master pages in the framework assembly. When I load the page in the browser, I get an error indicating that the master page doesn't
I would greatly appreciate any pointers on referencing a master page built into an assembly from a page in another project.
Apr 12, 2006 03:43 AM|LINK
My suggestion would be to look at using a VirtualPathProvider. Unlike UserControls, which we can load by Type or from a physical .ascx file, I think the runtime is always going to look for a .master file on disk. With the VirtualPathProvider you can make
the .master file appear as if it is on disk. Good article on the topic here:
This seems like an interesting project. I'd like to try it sometime. Let me know if you can make some progress.
Oct 27, 2006 06:15 PM|LINK
Oct 27, 2006 07:41 PM|LINK
Oct 28, 2006 06:03 AM|LINK