WiX 和 Visual Studio Web 部署项目的问题
我们想要从 Visual Studio 2008 中的 Web 部署项目创建 .MSI 包。 现在我们想要使用持续集成，并且需要在夜间构建中构建 .MSI 包。
到目前为止，我们使用标准的 Visual Studio Web 安装项目，但这与 MSBuild 不兼容。所以我们决定使用 WiX。
问题是我还没有找到任何关于此的好的教程/文档。 有没有办法从 Web 部署项目中制作 WiX 安装程序包？如果是，如何？
另外，我尝试使用 heat.exe 为 WiX 项目 .wxs 文件创建 XML，但 heat.exe 似乎无法识别 Web 部署项目格式。
感谢您的回复。
问候，
五、
We want to create an .MSI package from a web deployment project in Visual Studio 2008.
Now we want to use continuous integration and we would need the .MSI package build in the nightly builds.
Till now we used standard Visual Studio Web Setup project, but this is not compatible with the MSBuild. So we decided to use WiX.
The problem is that I have not found any good tutorial/documentation about this.
Is there a way to do a WiX installer package from a web deployment project? If yes, how?
Also, I tried to use heat.exe to create the XML for the WiX project .wxs file, but it seems that heat.exe doesn't recognize the web deployment project format.
Thank you for your responses.
Regards,
V.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我最近写了一篇关于此的博客文章 - http://www.chrissurfleet.co.uk/post/2011/07/01/Using-Packages-Project-Output-in-WiX-and-Visual-Studio.aspx< /a>
简而言之，使用 msbuild 打包您的 Web 应用程序，然后将其传递给 heat 来生成安装程序相当容易。
希望这有帮助。
I wrote a blog post about this recently - http://www.chrissurfleet.co.uk/post/2011/07/01/Using-Packaged-Project-Output-in-WiX-and-Visual-Studio.aspx
In short, its fairly easy to use msbuild to package up your web app and then pass it to heat to generate your installer from.
Hope this helps.
您可能早就找到了解决方案，但为了详细说明 Tom Cabanski 的答案，您可以通过构建中的外部进程使用“devenv.com”在命令行上调用 Visual Studio 来构建 msi。它不像使用 msbuild 那样漂亮，但它可以完成工作。下面是如何调用 Visual Studio 的示例：
其中 your.sln 是您要构建的解决方案的解决方案文件，Release 是您要构建的配置构建，确保您选择的配置实际构建 vdproj 项目。
成功执行后，您可以从相应的配置箱中获取 msi，并用它执行您想要的操作。
我很感激您用您的发现/方法对此做出回应，因为我正在尝试决定是否采用 WiX 或 InstallShield 作为在 TFS Build 中为 Web 应用程序构建 msi 的方法，或者继续使用我刚才描述的方法。我还没有机会尝试 WiX，而且我对 InstallShield 的了解非常有限，这表明这远远不能满足我的需求，即为一些相对直接的 Web 应用程序到公司内部网提供简单的部署帮助通过 TFS 构建。
You've probably long since found a solution for this, but to elaborate on Tom Cabanski's answer, you can invoke Visual Studio to build the msi on the command line using "devenv.com" via an external process from within your build. It's not a pretty as using msbuild, but it gets the job done. Below is an example of how to invoke Visual Studio:
Where your.sln is the solution file for the solution you wish to build, and Release is the configuration you wish to build, ensuring that the configuration you choose actually builds the vdproj project.
Following the successful execution, you can grab the msi from the appropriate configuration's bin, and do what you want with it.
I'd appreciate your response to this with your findings/approach, as I'm trying to decide whether to adopt WiX or InstallShield as the approach to building msi's for Web Applications within TFS Build, or to continue with the approach I just described. I haven't had to opportunity to try WiX out, and my very limited exposure to InstallShield suggests that this is far to involved for my need, which is to produce a simple deployment aid for some relatively straight-forward web applications to the company intranet via TFS Build.
我们在最近几个项目的安装程序上使用了 WIX，但最终后悔了。我会坚持使用 VS 内置项目，只在 CI 构建中从命令行调用 VS IDE。
We used WIX on the installers for our last couple of projects and ended up regretting it. I would stick with the VS built-in projects and just invoke the VS IDE from the command line in the CI build.