views:

198

answers:

2

I have a Visual Studio setup project that installs an application into the task scheduler and also installs a GUI application to manage some configuration parameters in the registry. This being the case, the setup project installs two different primary outputs (.exe's) as part of the process.

I am getting the following warning when I rebuild the setup project:

Configuration file 'C:\my\App.Config' is being used to configure all executables

Is there any way to remove this warning? The suggested MSFT solution apears to be to use a different setup project for each .exe, but I only want the users to have to run one installer. Any suggestions?

A: 

Maybe you could create an installer that launches all the other installers. This isn't a particularly helpful on microsofts part is it?

Another idea might be to take their advice and use either no config file or a custom file format so that you avoid this error.

Wardy
I actually tried launching one installer from the other and it gave me an error saying another installer was already running. I'm sure this idea of having one installer launch multiple others is possible. I'm just not sure how to do it with the default installer tools in VS.
Taylor Leese
A: 

There was a <runtime> section in my App.Config file and once I removed this portion of the config file the issue went away.

Taylor Leese
If the runtime was the only content in your config file then you could simply delete the file.
Cedrik