You've probably seen the cool announcements from Microsoft about the new Community Edition of Visual Studio and the upcoming Visual Studio 2015 release in the new year. We at the NuGet team have been ramping up our tools to support the new Visual Studio with a better visual experience and a better command-line experience. We've also released some i...
On November 12, 2014, as part of the Visual Studio 2015 Preview release, we released NuGet 3.0 Preview. This is a big release for us (albeit a preview), and we're excited to start getting feedback on our changes. Visual Studio 2012+ This NuGet 3.0 Preview is included in Visual Studio 2015 Preview. We are working to get preview drops out for Visua...
As we work on the designs for getting NuGet in the platform, it has become clear that NuGet needs better support for carrying arbitrary artifacts in packages and exposing them for consumption after the initial package installation. Conventional Manifests Since NuGet's initial release, it has supported conventional manifests and only a few concept...
I recently declared that NuGet is "Broken By Design." Now, that was hyperbolic; I don't really think NuGet is broken. In fact, I'm very pleased with NuGet (and proud of it). But I wanted to make the point that NuGet's approach both earned it success but also came at a cost. NuGet can't presently offer some expected package management features becau...
On January 13, 2011, NuGet 1.0 was released with ASP.NET MVC 3. On June 19, 2012, NuGet 2.0 shipped in the box with all editions of Visual Studio 2012 (including the free ones). That was a little over 2 years ago, and NuGet's adoption has been steadily increasing since then. Here are some interesting figures for recent NuGet usage from nuget.org: ...
As NuGet continues to gain momentum, more Microsoft teams have been seeking to install NuGet packages from their Visual Studio tooling. This began with ASP.NET, where NuGet was born, when project templates started coming with pre-installed NuGet packages. More recently, we've heard of teams all across Microsoft with tooling gestures that result in ...
As we work on some big changes for NuGet 3.x, we're finding that we're at a crossroads: Should we use .NET 4.5 and improve our Visual Studio UI using new features available in Visual Studio 2012, Visual Studio 2013, and Visual Studio "14"; or should we retain support for Visual Studio 2010? Visual Studio 2010 has been supported since NuGet's intro...
Have you ever seen this error before? Doesn't it make you want to yell and scream at NuGet, "Why did you just show it to me if I couldn't install it!?‽" Yeah, it makes us want to yell and scream too, so we decided to set about fixing it! Along with that, we've also discovered a bug we want to correct but unfortunately, it's a breaking change so...
Updated Sept. 2015: Our roadmap and requirements have changed and we have yet to implement these features as of NuGet v3.2. We are tracking this issue on GitHub. Please track this issue to follow our progress. We adopted Semantic Versioning (SemVer) in NuGet 1.6. At the time, SemVer 1.0.0 was the current version of the spec. Adopting SemVer provid...
The Warehouse is Dead, Long Live the Warehouse! Back in June, we blogged that our package statistics were full of lies. We made a fix and expected reports to become correct on June 26th. When June 26th came and went though, we discovered that the numbers were still questionable. Since then, we've identified a few other issues leading to invalid st...
