TFS和库在nuget中不可用

Question

So we have a ASP.net MVC 4 solution that is composed of the 3 projects BusinessLibrary.UI, BusinessLbrary.Domain, BusinessLibrary.Tests

We use nuget to manage all of our libraries like json.net, entity, etc. But we also have some private libraries that we have added. What is the best way to manage of the private libraries we have. I would like to be able to have a new developer to get all the DLL's associated with this project when they start.

Ive read that I could create a library or lib folder, and then just reference the DLL's to there. But should that be checked in with the Project' s Source Control then? Would I only want to copy over the non-nuget private libraries. Is this the best way to go?

What is the standard practice for situations like this, how should I be storing my private libraries?

Answer 1

Personally, I create a dependencies folder at the solution level. I put all non-NuGet libraries that I reference there. When I add the reference, I'm sure to reference the assembly from the dependencies folder. Make sure you add the dependencies folder to Source Control.

That way any developer pulling down the solution from Source Control will automatically have the correct version of all of the dependencies.

Answer 2

您可以选择安装自己的NuGet服务器，并在成功构建这些库之后将库放在那里

Answer 3

We create a library directory, add the assemblies there and use relative paths to reference them. We also check in this directory, so every team member immediately has the newest assemblies.

Another option would be to setup a private NuGet feed (such as MyGet) and publish your assemblies there as packages.

Answer 4

In our project we created lib folder for private dll's and checked in it to TFS along with source code. NuGet packages are added to TFS automatically.