在Visual Studio 2013中,我们仍然对安装程序项目.vdrpoj或WiX感到困惑吗? [英] Are we still stuck with installer projects .vdrpoj or WiX in Visual Studio 2013?
问题描述
Visual Studio 2013 安装程序项目还是 WiX ?
自 Visual Studio 2008开始,我就有一个.vdproj和一些WiX项目,现在我需要迁移到Visual Studio2013.仍然需要使用相同的两个项目类型还是有更好的解决方案?
I have a .vdproj and some WiX projects since Visual Studio 2008 which I now need to migrate to Visual Studio 2013. Do I still have to use the same two project types or is there a better solution?
仍然不支持设置项目, MSBuild 和WiX项目仍然是XML(尽管我现在可以购买视觉设计师).
Setup projects are still not supported with MSBuild and the WiX projects are still XML (although I see a visual designer is now available to purchase).
我讨厌他们两个.我需要可视的东西,MSBuild支持.我们也有许多自定义操作.
I am sick of both of them. I need something that is visual and that is supported by MSBuild. We have many custom actions too.
推荐答案
WiX是免费解决方案的默认方法,这些解决方案需要执行高级步骤并且必须能够集成到Team Build和
WiX is the default way to go for free solutions that need to do advanced steps and must be able to integrate into Team Build and MSBuild.
Product Free/Paid VS designer MsBuild Support
InstallShield LE free yes yes
InstallShield Pro paid yes yes
InstallAware paid yes yes 3)
Advanced Installer free yes yes
NSIS free no no
MS VS Installer Projects free yes no
Wix Toolset free no 1) yes
InnoSetup free no no
PS App Deploy Toolkit free no 2) no
备注:
- 是扩展名似乎支持WiX的用户界面
- 由于它基于 PowerShell ,因此您可以使用生成与MSBuild兼容的
.*proj
文件.
- There is an extension that seems to support a user interface for WiX
- Since it's PowerShell based you could use the Visual Studio PowerShell Tools.
- Advanced Installer can generate an MSBuild compatible
.*proj
file on request.
产品链接:
- InstallShield
- 安装Aware
- 高级安装程序
- Microsoft Visual Studio安装程序项目2013
- WiX工具集
- WiX Visual Studio扩展
- NSIS
- InnoSetup
- PS AppDeploy工具包
- InstallShield
- Install Aware
- Advanced Installer
- Microsoft Visual Studio Installer Projects 2013
- WiX Toolset
- WiX Visual Studio extension
- NSIS
- InnoSetup
- PS AppDeploy Toolkit
请记住, Team Build 2013具有一组本机扩展点,可让您执行以下操作:生成后执行PowerShell脚本,几乎可以触发所需的每种安装程序类型.可以相对轻松地触发基于非MSBuild的系统,例如PS AppDeploy工具包或 NSIS
Remember that Team Build 2013 has a set of native extension points that allow you to execute PowerShell scripts after build which can trigger pretty much every type of installer project you need. Non-MSBuild-based systems like the PS AppDeploy Toolkit or NSIS can be triggered with relative ease this way.
基于XML和基于脚本的UI通常更易于合并和分支,并随着时间的推移提供更好的可维护性,因为您几乎可以自由地在单独的文件中定义模块并提供有关为什么的注释部署在何处或何时执行哪些命令.
XML and script-based UI's are generally easier to merge and branch and provide better maintainability over time as you're pretty much free to define the modules in separate files and provide comments on why certain files are deployed where or which commands are executed when.
这篇关于在Visual Studio 2013中,我们仍然对安装程序项目.vdrpoj或WiX感到困惑吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!