这是OpenWrap和的NuGet之间的差异。和你preFER？

What is the difference between OpenWrap and NuGet. And what you prefer ?

推荐答案

OpenWrap是一个开放源代码项目中的应用，不仅在制作的时候，而且在运行时提供依赖管理。

OpenWrap is an open-source project providing for dependency management in applications, not only at build time but also at runtime.

因此​​，我们的特点是针对性的相关性动态清晰度，无论是复合WPF应用程序，Web应用程序开发或系统范围的实用程序。这使我们实现从什么的NuGet确实有很大不同。

As such, our features are targetted at dynamic resolution of dependencies, be it for composite WPF applications, web app development or system-wide utilities. This makes our implementation very different from what NuGet does.

因此​​，这里是不同的东西（我可能会忘记了很多，但很好啊）。

So here are the things that are different (I'll probably forget a lot, but ah well).

在Visual Studio中无依赖，并专注于生产效率的命令行，而不是在用户界面 在PowerShell中无依赖，OW都有自己的指令系统，可以让你开发，部署和执行自己的命令，无论是从我们的壳（中o.exe工具）或MSBuild的本身。 OpenWrap使用OpenWrap来构建和部署本身，就是XCOPY友好在每一步的方式。 的包的全系统的资源库，这样你就可以部署工具命令一次，而不是每一次的解决方案 支持在运行时动态依赖关系，如果你想这样做， 有一个可扩展封装格式，这样你就可以在一个包中创建新的类型的依赖关系，并有OpenWrap帮助您使用它们在你的应用程序 同时支持OpenWrap包和的NuGet包和​​存储库 住在远离XML和OData的并发症，而只是以简单的文本为基础的DSL，很容易和快速学习 支持集成构建，这样你就可以构建和一次性打包的解决方案 支持网络共享，你可以从openwrap壳或的MSBuild任务发布到定制库 提供的依赖练级，自动选择软件包版本的哪个组合都解决了 在ReSharper的集成，这意味着你做你的依赖关系的任何变化得到反映VS实时 在TeamCity的整合意味着您可以构建，打包和使用完全相同的过程部署软件包，从一个MSBuild的脚本或命令行 在可扩展的建设者意味着你可以更改构建的内OpenWrap触发 支持测试运行和运费一起包检查 使用支持的MSBuild扩展点，包括程序集引用，并留下c您独自建造了$ C $。一旦你船的二进制文件，你有没有openwrap code依赖的，只有在编译时。 No dependency on visual studio, and focus on productivity at the command-line rather than in a UI No dependency on powershell, OW comes with its own command system that lets you develop, deploy and execute your own commands, be it from our shell (the o.exe tool) or from MSBuild itself. OpenWrap uses OpenWrap to build and deploy itself, and is xcopy friendly at every step of the way. Has a system-wide repository of packages, so you can deploy your utility commands once rather than once per solution Supports dynamic dependency resolution at runtime, should you want to do that Has an extensible package format, so you can create new types of dependencies in a package and have OpenWrap help you use them in your application Supports both OpenWrap packages and NuGet packages and repositories Stays well away from the complications of XML and OData, and goes for simple text-based DSLs that are easy and quick to learn Support integrated build, so you can build and package your solution in one go Supports custom repositories on a network share that you can publish to from the openwrap shell or the msbuild tasks Provides dependency levelling, automatically choosing which combination of versions of packages are resolved Resharper integration means that any change you do to your dependencies gets reflected in VS in real-time TeamCity integration means you can build, package and deploy your package using exactly the same process, from an MSBuild script or from the command-line Extensible builders means you can change how the build is triggered within OpenWrap Support for test runners and shipping tests alongside packages Uses supported MSBuild extensibility points to include assembly references, and leaves the code you built alone. Once you ship binaries, you have no openwrap code dependency, only at build-time.

这只是为了区别，因为这是你问什么，所以我不会打扰你与我们做同样的其他包管理器。

That's just for the differences, as that's what you asked about, so I won't bother you with what we do the same as other package managers.