views:

978

answers:

2

Hi,

I want to make my build process for producing a setup project to be a single click. However, I also want to add {smartassembly} to the build step to obfuscate the build, but only on our build machine. How can I add a pre-build step to a visual studio 2008 vdproj?

Basically, I want to move the command line argument to obfuscate the build from the end of building the application to part of the setup program, so only the build machine needs to have a license.

Alternatively, should we just get {smartassembly} for all of our developers? It's a very large cost change (going from one build license to 5 is not a trivial amount of money), so the reasoning here has to be pretty airtight. I was going to add it to just the machine responsible for the build, rather than having all developers have it, and then force developers to try to reproduce bugs in the release build that customers actually have.

A: 

Why not have a different target/build/configuration for your solution/projects. It is the only one built on the build machine.

(pre/post build step only for that project/target/configuration)

If that doesn't work, I'd ask the company who wrote it their suggestions.

Tim
I haven't figured out how to do different build configurations for a setup project in visual studio. I think the company certainly wouldn't mind selling the extra four licenses :)
mmr
oh - sorry, I missed the part about vdproject/installer project. This has got to be a common issue for them though.
Tim
yeah, it turns out I'm a moron. The UI is different, but the pre- and post- build items are in the properties as if it were a UI property, not a project property.
mmr
+1  A: 

yeah, it turns out I'm a moron. The UI is different, but the pre- and post- build items are in the properties as if it were a UI property, not a project property.

mmr