Last post Jun 01, 2007 04:01 PM by jhahn
Jun 01, 2007 04:01 PM|jhahn|LINK
I followed the guide on this page
http://support.microsoft.com/kb/307467 "How To Create an ASP.NET Application from Multiple Projects for Team Development" and I now have my main app at the root of the application and I have all of the sub applications as sub directories of the root application.
It all works great when I do a normal debug build or a normal publish.
The problem is that I have nested sitemaps, nested master pages, and of course, nested web.config files. Basically the root app has a master page, sitemap, and web.config file and each child app also has it's own master page, sitemap, and web.config file,
but they are nested, so the sub master page inherits the layout from the root master page and adds whatever that specific app needs to add (like the menu layout, etc). When the application is "debugged" or "published", it builds everything together and all
of the sub apps inherit these things from the main app and it works great. Now I am at a point where I am ready to use web deployment projects to dynamically alter the web.config files for different environments. (We have test and production servers and
I need a way to easily switch.) Trying to build this nested projects setup via web deployment projects doesn't work because WDP tries to build each of the sub projects independently. Since the sub-apps are reliant on inheriting the web.config, site.master,
and web.sitemap files from the root application, they spit out a bunch of "cannot find ~/site.master, etc errors. And the build doesn't get created.
Basically, I just want to know how to use WDP with the multiple application structure listed in the article above.
Thanks in advance for the help.