自动发布脚本和 Visual Studio 安装项目
我想这里的大多数人都了解完全自动化构建的重要性。
问题是我们的一个项目现在使用集成的 Visual Studio 安装项目 (vdproj)，并且最近已移植到 Visual Studio 2008。不幸的是，这些项目不会在 MSBuild 中构建，并且在 2008 上调用 devenv.exe /build 只会崩溃，显然它在所有多核计算机上都这样做（!!!）。 因此，现在我可以选择回滚到 .Net 2.0 和 2005，或者干脆放弃 Visual Studio 部署，但首先，我想听听其他意见。
任何人都知道另一种自动构建 .vdproj 的方法，不需要我们打开 IDE 并单击内容？
当我说我们将放弃 vdproj 时，我想到的就是 WiX。 你有这方面的经验吗？好东西，注意事项？
I think most people here understand the importance of fully automated builds.
The problem is one of our project is now using an integrated Visual Studio Setup project (vdproj) and has recently been ported to Visual Studio 2008. Unfortunatly, those won't build in MSBuild and calling devenv.exe /build on 2008 just crashes, apparently it does that on all multi core computer (!!!). So now I have the choice to either rollback to .Net 2.0 and 2005 or simply ditch Visual Studio deployement, but first, I'd like a second opinion.
Anyone knows of another automated way to build a .vdproj that will not require us to open the IDE and click on stuff?
WiX was what I had in mind when saying we would ditch vdproj. Do you have any experience with it, good things, caveat?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我有同样的要求，最终使用了这两个链接中建议的内容
大卫·威廉姆斯博客
MSDN 文章
基本上，由于 Team Build 本身不会为您构建安装项目，因此这种方法让您在常规构建完成后添加新的构建步骤。 此步骤通过启动 devenv.exe 来启动第二个构建。 IDE 将构建您的安装文件。 额外的构建有点昂贵，但我们只需要它用于即将推出的构建。 每日构建最多需要这种定制，而我们的 CI 构建不需要每次都构建设置文件。
之后，您执行一些复制命令，再次构建显示在团队系统构建结果中的步骤，将安装文件移动到网络共享等。
一开始感觉有点像克鲁格，但它确实有效，它是也是团队系统中自动化构建的成熟部分，因此它有助于我的持续集成目标。
I had the same requirement and ended up using what is suggested in these two links
David Williams Blog
MSDN article
Basically, since Team Build, by itself, will not build the setup projects for you, this approach has you add a new build step after the regular build is complete. This step fires off a second build by launching the devenv.exe. The IDE will build your setup files. The extra build is a bit costly but we only needed it for builds that were going to be pushed out. The Daily build at most would need this customization our CI build does not need to build setup files each time.
After that you execute some Copy commands, once again build steps that show up in your Team System build results, to move the setup files to a network share etc.
It feels a bit like a kluge at first, but it does work, it is also a full-fledged part of the automated build in Team System so it worked for my Continuous Integration goals.
低成本解决方案是改用 ClickOnce，您可以使用 MSBuild 实现自动化。 但是，如果您仍然需要创建 Windows Installer 程序包，则需要将项目转换为 WiX（非常简单）并使用您的解决方案进行构建。
这将帮助您开始：
使用 MSBuild 和 Windows Installer XML 自动发布
The low cost solution is to switch to using ClickOnce, which you can automate using MSBuild. But if you still need to create a Windows Installer package, you will need to convert your project to WiX (pretty straight foward) and build that with your solution.
This will get you started:
Automate Releases With MSBuild And Windows Installer XML
我以前使用过 WiX，一般来说，我发现一旦你弄清楚要做什么，它就很棒，但学习曲线很陡。 如果您花一整天时间学习 WiX 教程，您应该能够使 80% 的设置正常工作。
WiX 工具集教程
I've used WiX a little bit before, and generally I found that it's great once you figure out what to do but there is a steep learning curve. If you spend a solid day going over the WiX tutorial you should be be able to get 80% of your setup working.
WiX Toolset Tutorial