The vdir method works good. We also create a base page and deploy it in the GAC that has utility classes for the master page.
http://strangeworld:8081 has more details and a working example.
--------------------------------------------------------------------------------
Storing the master page in the GAC was not a tested/supported scenario. It seems to work, but considering it wasn’t a tested scenario, I wouldn’t recommend it. (VSWhidbey 569807):
1. Scott's article about copying the precompiled dll to the application directory works.
http://weblogs.asp.net/scottgu/archive/2005/08/28/423888.aspx
2. This kb about creating virtual directory underneath the application and point to the shared master page, user control or sitemap would also be recommended and supported way.
324785 How to ahare ASP.NET pages and user controls between applications by http://support.microsoft.com/?id=324785
--------------------------------------------------------------------------------
There was another post about this a little while ago on the list, there appears to be a rather convoluted option based on the GAC described here
http://weblogs.asp.net/dwahlin/archive/2005/11/16/430779.aspx
Samuel
--------------------------------------------------------------------------------
Hi,
is there a way to share a master page between different web projects? I would like to have something like a link that we can add to every project (the same feature that is available in other project types), so updates will be propagated to all referencing projects.
Unfortunately, the source control system (CVS) does not support creating linked files. Any other techniques we could use to facilitate this?
thx,
- patrick
Patrick Schuler
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment