In VS2003, one could specify a "Configuration Override File" in a Project's Configuration Properties\Deployment tab which would be used to override/replace the app.config (generated as myexe.exe.config) with the specified config file when a deployment project was built.

I am trying to find the equivalent capability in VS2005. The Project's Deployment tab seems to be gone, and I can't find anything in the deployment project which looks like it.

Can anyone help, or give me some guidance as to how to achieve the
equivalent result in VS2005?

Thanks

Jeff Mason
Custom Apps, Inc.
[email protected]

__________________
-- Jeff

Lots of views, no replies. :(

I have an answer, of sorts.

After some conversations with some MS folks, I found that in its infinite wisdom, MS removed this option in VS2005. They mumbled something about Team Server and the problems this option caused managing config files in the Team Server environment.

They are also reconsidering that decision, though I wouldn't hold my breath...

In any case, we got around this via a hack by creating a number of app.config files, one for each build configuration. For example, I created an app.test.config and app.release.config which corresponded to the settings required for the test and release builds.

Then, I created a set of pre-build event commands which tested the about-to-be-built configuration and copied over the appropriate app.<build>.config over the app.config in the project, as:

IF $(ConfigurationName)==Debug (COPY /Y "$(ProjectDir)app.dev.config" "$(ProjectDir)app.config")
IF $(ConfigurationName)==Release (COPY /Y "$(ProjectDir)app.release.config" "$(ProjectDir)app.config")
IF $(ConfigurationName)==Test (COPY /Y "$(ProjectDir)app.test.config" "$(ProjectDir)app.config")

This insured that the appropriate app.config was available at build time for the installation/deployment project.

The app.<build>.config files are under source control, app.config is not, so it can be overwritten.

Bah.

Jeff Mason
Custom Apps, Inc.
[email protected]