管理非nuget dll和nuget包 [英] managing non-nuget dlls along with nuget packages

问题描述

大多数这些可能是第三方库，可能会有一些指导方针或建议来管理那些不在nuget上的图书馆。除非我们专门把它们放在nuget上，否则永远不会去nuget。

最好将这些dll与nuget用于存储下载的DLL的文件夹保持一致还是更好将它们保持在一起？

一旦我们整理出来，我们将会考虑移动到DVCS，并且可能会添加一个忽略文件来忽略整个包目录（并且可能添加排除这些非nuget dll或只是强制他们进行检查，如果他们有任何改变）。

解决方案

我的个人偏好（订单）

1. 创建一个包并将其添加到NuGet（如果许可允许）


2. 创建一个包并将其放在私有存储库中


3. 在解决方案中创建一个文件夹，将它们全部存储在re，将它们添加到源代码控制。不同的文件夹比nuget包文件夹，因为它是更清楚的是什么，我不添加nuget dll到源代码控制。

对于1 &安培; 2我建议在构建中使用Restore Package，而不是将其存储在源代码控制中。

我还强烈建议您不要从安装文件夹引用任何第三方控件GAC。

Are there any guidelines or recommendations for managing libraries that aren't on nuget along with the packages that are.

Most of these may be 3rd party libraries that may never go on nuget unless we specifically put them on.

Is it best to keep these dlls out of the same folder that nuget uses to store its downloaded dlls or is it better to keep them together?

We would be looking at moving to DVCS once we sort this out and would probably add an ignore file to ignore the whole packages directory (and possibly add exclusions for these non-nuget dlls or just force them to be checked in if they ever do change).

解决方案

My Personal Preferences (In Order)

1. Create a package and add it to NuGet (if licensing allows)
2. Create a package and put it in a private repository
3. Create a folder in the solution, store them all in there, add them to source control. Different folder than the nuget packages folder as it's clearer what it is and I don't add nuget dlls to source control.

For 1 & 2 i would recommend using Restore Package on build rather than storing it in your source control.

I'd also highly recommend against referencing any 3rd party controls from install folders or the GAC.

这篇关于管理非nuget dll和nuget包的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！