问题描述
让我们来讨论以下议题。还有目前正在部署具有很好的了解XCOPY method.This方法的应用使得难以管理的依赖关系，文件更新等。有主意，开始应用程序部署的一些软件包的帮助，你知道像你的Linux做帮助 RPM ，但适用于Windows。
Let's discuss following topic. There is application which currently is being deployed with good to know xcopy method.This approach makes difficult to manage dependencies, file updates etc. There is idea to start application deployment with help of some packages, you know like you do in Linux with help of RPM, but for Windows.
所以，我有一个问题：？什么包系统是更好地在Windows经典的Windows安装程序使用（ MSI ）或的NuGet 或其他什么东西
So I have question: what package system is better to use on windows classic windows installer (msi) or nuget or something else?
推荐答案
MSI 是公认的企业应用程序的标准。它有 一些大公司的好处 相比传统的部署技术。
MSI is the accepted corporate application standard. It has some major corporate benefits compared to legacy deployment techniques.
- 维克斯工具集下载 。
- 维克斯是新开源的方式来创建MSI文件。
- 要围绕让你的头维克斯，您可能需要阅读 快速的汇总其背后 历史。
- 然后，你可能想看看其他方式通过阅读来提供一个安装程序，除了维克斯： What产品安装使用？的InstallShield，WIX，英明，高级安装等
- 最后查看如何维克斯源文件及其组件看起来像的。这是在Hello World的维克斯的
- Wix Toolset Download.
- Wix is the new open source way to create MSI files.
- To get your head around Wix, you might want to read a quick summary of the history behind it.
- Then you might want to check other ways to deliver an installer, besides Wix by reading: What installation product to use? InstallShield, WIX, Wise, Advanced Installer, etc.
- Finally view a complete example of how a Wix source file and its components look like on Codeproject. This is the "Hello World" of Wix.
一些很好的起点链接了解维克斯：
Some good starting links to learn Wix:
- 我的维克斯快速启动建议
- Good学习如何从维克斯 创建MSI安装程序的资源
- 如何实现维克斯安装程序升级？
- 什么是维克斯和WiX的工具集的限制？
- My Wix quick start suggestions
- Good resources for learning how to create MSI installers from WiX
- How to implement WiX installer upgrade?
- What are limitations of WiX and WiX Toolset?
正如我在我的建议写了维克斯快速启动的帖子上面：维克斯是动手。 只注重简单，但想从的 - 独自阅读文档很可能仅仅是混淆的
As I wrote in my suggested "Wix quick start" post above: Wix is hands-on. Just focus on simple, but complete real-world samples like the one from Codeproject - reading the documentation alone is likely to be merely confusing.
专注于分裂您的应用程序在组件中，设置了一个重大的升级。 使用每个组件一个文件作为拇指的规则，阅读这个答案更好地了解组件创建的：的
Focus on splitting your application into components and set up a major upgrade. Use one file per component as a rule of thumb, and read this answer for a better understanding of component creation: Change my component GUID in wix?
一个重大升级是部署的软件最常用的升级机制（其他常见的升级类型是小幅度提升）。这显然是至关重要的，你可以升级你已经部署了。获取升级方案的工作部署之前，你的第一个软件版本，让你有信心，你的部署解决方案。
A major upgrade is the most commonly used upgrade mechanism for deployed software (the other common upgrade type is minor upgrade). It is obviously crucial that you can upgrade what you have deployed already. Get upgrade scenarios working before you deploy your first software version so you have confidence in your deployment solution.
一旦你有你的组件设置和升级的解决方案是工作，对其中的其余水到渠成当你在应用程序的部署要求，以你的方式，并检查样品的维克斯教程网站： http://wix.tramontana.co.hu/
Once you got your components set up and your upgrade solution is working, the rest of the pieces fall into place as you work your way through your application's deployment requirements and check for samples on the Wix tutorial site: http://wix.tramontana.co.hu/.
对于那些直接写维克斯code（不带图形用户界面编辑器），我建议你查一下这个答案的方式，让你的源文件简洁：的
For those writing Wix code directly (without a GUI editor), I suggest you check this answer for a way to keep your source files terse: Syntax for guids in WIX?
进一步阅读：
- Windows安装程序和创建维克斯 的
- <一个href="http://stackoverflow.com/questions/2202210/installer-capabilities-wix-vs-installshield-ex$p$pss?rq=1">Installer能力，WIX VS防爆的InstallShield preSS
- 的Installshield或维克斯
- Windows Installer and the creation of Wix
- Installer capabilities, WIX vs InstallShield Express
- Installshield or Wix
这篇关于微星VS的NuGet包：这是对持续交付更好？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！