This site uses cookies for analytics, personalized content. By continuing to browse this site, you agree to this use. Learn More
The latest news, updates, and insights from the NuGet team
October 23, 2014Oct 23, 201410/23/14As 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,
October 14, 2014Oct 14, 201410/14/14I 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.
October 10, 2014Oct 10, 201410/10/14On 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,
October 8, 2014Oct 8, 201410/8/14As 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 NuGet packages being installed.
October 2, 2014Oct 2, 201410/2/14As 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”;
October 1, 2014Oct 1, 201410/1/14Have 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,
