简体繁体 English

Visual Studio安装项目-添加预构建步骤

[英]Visual Studio Setup Project— adding prebuild step

原文 2009-02-12 20:49:51 8 2 visual-studio/ installation/ prebuild

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. 但是，我也想在构建步骤中添加{smartassembly}来混淆构建，但仅在我们的构建机器上进行。 How can I add a pre-build step to a visual studio 2008 vdproj? 如何向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? 另外，我们是否应该为所有开发人员都使用{smartassembly}？ 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. 我打算将其添加到负责构建的机器中，而不是让所有开发人员都拥有它，然后迫使开发人员尝试重现客户实际拥有的发行版本中的错误。

2 个解决方案

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. UI有所不同，但是构建前和构建后项目位于属性中，就好像它是UI属性，而不是项目属性一样。

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. 如果那行不通，我会问写它的公司他们的建议。