NuGet.org Archives | Page 3 of 5

NuGet Package Identity and Trust

Daniel JacobsonApril 17, 2017Apr 17, 201704/17/17

Update on 10/16/2017: Package ID Prefix Reservation is now live. The documentation can be found here. We want to start this post with a huge thanks to you, the NuGet community. Over the last several months we have been talking to many of you to get feedback on NuGet package identity and trust. We’ve learned so much from you and we hope that...

Introducing scoped API keys

Anand GauravFebruary 2, 2017Feb 2, 201702/2/17

Update 2/14 (05:00 PM PST): This feature is now live! Login to your nuget account and expand the API Keys section to see the new experience. Since last year, we have been working on several fronts to advance NuGet as a secure environment for package distribution. This post describes an experience that will allow you to have better control of ...

NuGet – Ending Windows XP support

Karan NandwaniJanuary 19, 2017Jan 19, 201701/19/17

At NuGet, we are constantly improving our security. One of the steps we are taking is to move our HTTPS end points to meet industry standards for algorithms and protocols. This means that connecting to nuget.org services from machines that don’t support modern cipher algorithms will no longer be supported (such as TLS 1.0 support in Windows ...

Changes to Expiring API Keys

Harikrishna MenonAugust 25, 2016Aug 25, 201608/25/16

In June, we published a blog post announcing Expiring API Keys. We received a lot of great feedback from the community about it. In retrospect, we did not do a great job explaining the motivation and reasoning for this security measure to the community. This post goes into more detail about why we introduced Expiring API Keys, the immediate ...

NuGet API key expiration

Maarten BalliauwJune 22, 2016Jun 22, 201606/22/16

Update 6/22 (2:15 P.M PST): We have a lot of feedback coming in from the community on this topic. This change will not have any impact for another 90 days at the minimum. We are reviewing your feedback and will discuss further how to achieve our goal of improved security of NuGet.org. We will have an update within the next 45 days. To continue...

Switching from WCF OData to Web API

Maarten BalliauwFebruary 16, 2016Feb 16, 201602/16/16

One of the less visible changes since we released NuGet 3.0 is that NuGet uses a new server "API v3". This new API is designed around high availability for critical scenarios such as package restore and installing packages. API v3 will be the way forward for NuGet while keeping "API v2" around for older NuGet clients. We will be making a big ...

Why did my package download count suddenly go up

Maarten BalliauwSeptember 30, 2015Sep 30, 201509/30/15

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. As it turns out, we overlooked something very important: in the old system (and by importing data, also in ...

Meet the new NuGet status page

Maarten BalliauwSeptember 28, 2015Sep 28, 201509/28/15

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. It not only shows whether individual services are up ...

Revised Download Counts and Package Statistics

Maarten BalliauwSeptember 24, 2015Sep 24, 201509/24/15

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. As a result we're happy to announce package statistics are...

NuGet.org server status

Yishai GalatzerJune 8, 2015Jun 8, 201506/8/15

For the last few weeks we have experienced a few hours of downtime a few times a week. The NuGet community was very engaged in sharing the issues both on Twitter, support@nuget.org, personal emails, and GitHub. We thank you for that and appreciate your patience. We realize NuGet.org is a center to many of the day to day activities of a .NET ...

The NuGet Blog