October 2014 | The NuGet Blog

Package Manifests

Jeff HandleyOctober 23, 2014Oct 23, 201410/23/14

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 co

NuGet: In the Platform

The NuGet TeamOctober 14, 2014Oct 14, 201410/14/14

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

NuGet : Broken By Design

The NuGet TeamOctober 10, 2014Oct 10, 201410/10/14

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.

Visual Studio Tooling Guidance

Jeff HandleyOctober 8, 2014Oct 8, 201410/8/14

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 resul

Discontinuing Updates for Visual Studio 2010

Jeff HandleyOctober 2, 2014Oct 2, 201410/2/14

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

Target Framework Filtering and a Pending Breaking Change

Andrew Stanton-NurseOctober 1, 2014Oct 1, 201410/1/14

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 ch

The NuGet Blog