Last post May 27, 2010 02:33 PM by ming chen
May 25, 2010 01:29 PM|lemkepf|LINK
I have a web application project that let's me supply 2 configuration settings within a VBPROJ file.
How can I do that? Thanks!
Web Deployment Project
web deployment projects
Web Site Project
May 25, 2010 02:57 PM|Ming Chen|LINK
The two setting that you did is for the WPP pipeline. (WDP2010 now also enable it through te command line. But you need to manually drop web.debug.config)
The one you try to disable web.config substitution is provided as a backcompat for Existing WDP project. (Someone in your team enable it.). Which use ConfigAPI to replace section of the web.config. I am guessing this is an old existing WDP project?
To disable it.
(I thought the snip you provide, it already disable it?)
May 26, 2010 08:31 AM|lemkepf|LINK
Basically what i'm trying to accomplish is this:
1. During an automated build of our "website project" using a "web deployment project" for vs2010 build a packaged zip file of our site.
2. Do not replace any of the configuration in the web.config
a. This includes doing the old basic substitution of config sections.
b. Or do the new web.debug.config substitution
3. I have within my project a web.config, a web.debug.config, a web.release.config. I want all 3 of those configs to exist inside the zipped package file.
I have set <UseWebConfigReplacement>False</UseWebConfigReplacement>,
<TransformWebConfigEnabled>False</TransformWebConfigEnabled> . But yet it still replaces the configuration and removes the web.debug.config,
web.release.config from the zip file.
Thanks for the help!
May 26, 2010 05:30 PM|Ming Chen|LINK
Ah, I take a quick look. There is no easy way to do that in WAP But for WDP there is.
However, for the website and WDP. There is, you can set.
Try it and let me know if that weks for you.
May 27, 2010 11:03 AM|lemkepf|LINK
Yes, i believe that worked. Is there any reference documentation on that?
May 27, 2010 02:33 PM|Ming Chen|LINK
We just release WDP2010 RTW on May/25.
The documentation is lacking.
You are probably one of the first in the trying out the Packaging/webconfig transformation that it enable website project to leverage.
It includes a lot of workaround for WDP to leverage the VS2010 package/webpublishpipeline.
This is one of the targets to enable web.debug.config to have the item metadata that WPP need to perform tranformation.
We will try to detail those through the blog post as need to.
We are also planning on getting the general Packaging/Publish setting into WDP in feature release.