Last week, we released our Revised Download Counts and Package Statistics that are now based on the raw logs of our CDN. For this to become reality, we had to also import data from our old statistics data warehouse into the new system.
On the server side we are working on boosting performance, scalability and reliability. We were also in need of a new status page to better communicate the status of the service. Without further ado: meet the new status.nuget.org!
We’re happy with this new incarnation of our status page.
In the last few months we have been hard at work on the NuGet.org backend. One of the things we’ve done is switch to a new CDN. This work is all about reinforcing the foundations of nuget.org so we provide a better service experience and be in a position to build new features reliably.
This is a guest blog, by Andrew Arnott from the Visual Studio team. Andrew was having performance issues with NuGet updating or installing packages from a UNC share. These issues where well known, and our solution in the past was to point people to http servers.
Today we are publishing the version 3.2 updates to the NuGet clients. We took customer feedback regarding issues and feature direction and assembled this release to address those immediate concerns. There are fixes available for a number of blocking issues and adds support for push and list for compliant V3 servers.
Today we are releasing nuget.exe 3.2-RC command line. In addition to fixing a significant number of bugs, support has been added for push and list for compliant V3 servers.
This wave also includes a release of the visual studio extension version 3.2-RC.