Visual Studio 安装项目——添加预构建步骤
我想让我的构建过程只需单击一次即可生成安装项目。 但是，我还想将 {smartassemble} 添加到构建步骤中以混淆构建，但仅限于我们的构建机器上。 如何向 Visual Studio 2008 vdproj 添加预构建步骤？
基本上，我想移动命令行参数来混淆构建，从构建应用程序的末尾到安装程序的一部分，因此只有构建机器需要拥有许可证。
或者，我们是否应该为所有开发人员获取 {smartassemble}？ 这是一个非常大的成本变化（从一个构建许可证到 5 个构建许可证并不是一笔小数目），因此这里的推理必须非常严密。 我打算将其添加到负责构建的机器上，而不是让所有开发人员都拥有它，然后迫使开发人员尝试在客户实际拥有的发布版本中重现错误。
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.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
是的，事实证明我是个白痴。 UI 不同，但构建前和构建后项目位于属性中，就好像它是 UI 属性，而不是项目属性一样。
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.
为什么不为您的解决方案/项目设置不同的目标/构建/配置。 它是唯一一个在构建机器上构建的。
（构建前/构建后步骤仅适用于该项目/目标/配置）
如果这不起作用，我会询问编写它的公司的建议。
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.