Can I force the installer project to use the .config file from the built solution instead of the original one?

Viewed 8379

I am using the solution to this question in order to apply configuration changes to App.config in a Winforms project. I also have an installer project for the project that creates an installable *.msi file. The problem is, the config file bundled in the installers is the original, un-transformed config file. So we're not getting the production connection strings in the production installer even though the config file for the built winforms project has all the correct transformations applied.

Is there any way to force the installer project to use the output of project build?

7 Answers
Related