Wow. The results actually surprised me. I can't imagine working without NuGet. Maybe it depends on the type of application you are writing? I'm using ASP.NET MVC, and NuGet is a godsend for adding packages to my projects.
Anytime I start a new project, I immediately open up the NuGet command line and update Entity Framework, add in Ninject, NUnit and Moq, Elmah, etc., with just a few quick commands. Packages like Ninject.MVC3 and Elmah all come pre-configured, too.
It's so tedious to add all this in without it. Seriously? So many don't want to use it? It saves me a ton of time and effort.
The world is going to laugh at you anyway, might as well crack the 1st joke!
My code has no bugs, it runs exactly as it was written.
To be honest, I'd not heard of it.
But when I looked before answering this question, my response become "No, and I have no plans to".
There are enough bits of software (I'll be polite, this is family page) that check and auto update themselves on my PC already. Do I really want something that automatically updates a library I use, and potentially breaks an application without me knowing and testing it? No. No, thanks!
Typo - OriginalGriff[/edit]
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
It doesn't auto check and update without asking you, it's a packet manager for .NET.
It automates the process of managing 3rd party dependencies. You click the button, type whatever you want to add - it adds. You click the button to update, it updates. You click the button to remove dependency, it cleans up everything for you.
I've switched quite a few projects of mine from manual externals management to NuGet and haven't seen any downside yet.