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.
Post by this author
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,
With the NuGet 1.8 release, we found a breaking change that caused NuGet to fail on Windows XP machines. Earlier today, we released a hotfix to NuGet 1.8 that addresses this.
We apologize for any inconvenience this issue may have caused.
We’re happy to announce that we released NuGet 1.8 on 5/23/2012. This release includes support for localized satellite assemblies, nuget.exe performance improvements, and 34 bug fixes. Details are in the NuGet 1.8 Release Notes.
Known issue on Windows XP
We would like to call out that shortly after NuGet 1.8 was released,
We’re happy to announce that we released NuGet 1.7 today. This release includes several new features as well as over 75 bug fixes. Details are in the NuGet 1.7 Release Notes.
The NuGet Gallery was unavailable on March 9th from approximately midnight until 7:52 A.M., nearly eight hours. During this time all HTTP requests to the gallery website failed. In addition to affecting website users, the outage affected all NuGet client programs (such as the Visual Studio extension and nuget.exe) and other software that relies on the NuGet Gallery’s feed and API.
For the last few months, the NuGet team has been considering starting a proper, official blog. This is that blog.
How do we plan to use this blog? Here are a few ways we know we’ll use it (and I’m sure we’ll think of others as we go along):
Announcing new releases
Announcing upcoming breaking or very impactful changes
Pointing out particuarly important discussions on our CodePlex or GitHub sites
Feel free to leave us a comment,