All the examples I've seen for doing custom actions show the installer as being part of the application/project you are developing. What I need is a way to develop an installer that can reside in an assembly that isn't part of the application, but rather lives outside of it.

The following is what I am trying to accomplish

In our applications we have a configuration folder, with in that folder is the config files we have fore each environment and a shared folder for every environment. For example:

· Configuration

o Integration

§ web.config

o Production

§ web.config

o QA

§ web.config

o Shared

§ readme.txt

o Staging

§ web.config

This pattern is duplicated in every application we have, I want to write one assembly that will contain the installer, take a parameter from the install application and copy the appropriate files to the root of the application install, without having to include this assembly as part of the deploy as it is only required for the install.

Hopefully I'm missing something obvious here.
Wayne