It is possible to create a nuget 'master libs' type arrangement. I recall
doing it in my last role.
You create a nuget.config file in the same directory as the solution file
containing the shared location. It worked great
repositories
repository path=..\MyProject\packages.config /
I don't understand how it makes anything trickier.
Deployment is easy, all the assemblies are set as copy local = true.
having 3mb of files isn't a problem with source control, but there are
strategies around how you can make it NOT check those files in if you are
worried.
On 25 January 2012
I believe you can also make nuget packages for your own libraries that you
include in your projects, which means that your library is only in source
control once, as the project itself.
You may need a corporate nuget server for this, I'm not 100% sure..
On 26/01/2012 9:46 AM, David Burela
People have been talking about NuGet a bit so I thought I'd try it out.
The very first thing that confused me was the relationship between the NuGet
packages I install and those that I have already installed by other means.
For example I get packages for Entity Framework, Nunit and SQL CE, but
: The way NuGet works
People have been talking about NuGet a bit so I thought I'd try it out.
The very first thing that confused me was the relationship between the NuGet
packages I install and those that I have already installed by other means.
For example I get packages for Entity Framework
Hi Greg
Then I see that it has created a packages folder under my solution folder
containing 55 files in 4 folders with a total size of 3.8MB. Now this seems
a bit heavy-handed ... it will create duplicated and redundant files in
projects everywhere, multiple tool versions can be installed, and
Hi Greg,
Check out
http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packagesfor
details of how to get nuget to manage the dependencies without
checking
in all of those files into source control. This gets even more powerful if
you have a corporate NuGet server so that you get
