Oh you fancy huh?
In a nutshell:
meh…
What they say it is:
NuGet is a Visual Studio extension that makes it easy to add, remove, and update libraries and tools in Visual Studio projects that use the .NET Framework. If you develop a library or tool that you want to share with other developers, you create a NuGet package and store the package in a NuGet repository. If you want to use a library or tool that someone else has developed, you retrieve the package from the repository and install it in your Visual Studio project or solution.
http://docs.nuget.org/docs/start-here/overview
What it REALLY is:
Ruby Gems for Microsoft stuff…
Hype:
As expected, there is the hard sell from MS
http://channel9.msdn.com/Events/MIX/MIX11/FRM09
DISCLAIMER: No shots at Hanselman or Haack at all!
Beef:
- Seems it is automatically installed either with MVC or with VIsual Studio. Oh, Microsoft…
- How hard is it really to add a reference to a project? of all the challenges we face as Mircosoft developers, adding a reference is the least of my issues.
- Attempts to hoodwink us into believing this is revolutionary, simple and easy. So far, it hasnt been easier than right-clicking and adding a reference
I doubt I’ll bother uninstalling it, as the premise is a good one. If you dig PowerShell you might love it, if you find that right clicking and downloading and right-clicking again and adding a reference is too much work then this might be for you. Be warned, you STILL have to click a bunch of stuff to install it into your project and if you run into any hiccups like I did, you might wonder if its really making life easy? NuGet is worth a whirl and may help new frameworks get instant visibility and adoption. On the flipside, some developers will ONLY use ‘packages’ hosted on NuGet. Its a good tool to be familiar with just in case it becomes a trend but personally, I’m okay with downloading the frameworks I use and adding them manually without all the overhead of NuGet. Womp.
Be The First To Comment