views:

321

answers:

1

I have multiple Visual Studio 2003 Deployment projects that include the primary output of another project. One of the differences in the Deployment projects is that they use different primary output settings properties. These settings get copied to a PrimaryProjectName.exe.config file when I build the primary project, so currently my build process goes something like:

  1. Build primary project.
  2. Edit primary project .config file for deployment A.
  3. Build deployment A.
  4. Edit primary project .config file for deployment B.
  5. Build deployment B.
  6. Edit primary project .config file for deployment C.
  7. Build deployment C.
  8. ...

I would like to automate this process. I can build scripts to edit the primary project .config file for each deployment, but how can I run them when I build the deployment projects? My VS Application project properties includes a Build Events tab where I can define pre-build events that get run before building the primary output, but there is no such tab for Deployment projects.

Edit: Sorry I did not specify, this is a VS 2003 project targeting .Net 1.1. I know, but it's a client requirement.

A: 
oykuo
I did not mention this is for VS 2003. Yes, I know that's an important detail to omit, but the output must run in .Net 1.1.
Dour High Arch
I've attached a screenshot. This property is there in VS2005 too but I don't have VS2003 so can't check.
oykuo
I know this exists in VS 2005, but I cannot use that. VS 2003 does not have this property, check out this screenshot: http://i39.tinypic.com/2s5z72g.gif
Dour High Arch