Best IT Recipes

Nuget: should I transfer the entire contents of the package folder?

I started using nuget and installed some packages, most of which are 200 KB in size, but NUnit has 3 MB .

My solution is open source and loaded by a lot of people, I just think: should I transfer the entire package folder as it is, or ignore files without a DLL.

how are you guys doing?

+44
asp.net-mvc nuget
Dec 17 2018-10-17
source share
3 answers

Personally, I would include the entire package folder. There is nothing worse than getting an open source project, and then tracking down the dll you need to run it.

You can simply include the .nupkg files and force the user to run the service pack, but then you assume that they have nuget installed and do not forget to run it.

I think that it is much faster to get it open-source project has everything you need.

+16
Dec 17 '10 at 15:59
source share

NuGet now has the ability to reload the missing packages as a pre-build step, which means you only need to commit the packages.config file (and include nuget.exe in the tools folder).

Read Using NuGet without committing packages for source control for more details.

+77
May 26 '11 at 7:33 a.m.
source share

To repeat what Simon said is 2010. Bandwidth and storage are cheap on this scale. The convenience of having packages with a source exceeds all expectations.

+3
Dec 17 '10 at 16:10
source share


More articles:


All Articles