Feature Announcement

Introducing Source Code Link for NuGet packages

August 27, 2018 Aug 27, 2018 08/27/18

Maxime Rouiller

NuGet.org now supports surfacing source code repository link for NuGet packages. This will enable package authors to surface both the project's website and the source repository using the projectUrl and the repository properties respectively instead of having to choose between the two using just the projectUrl property. The nuspec has ...

Introducing signed package submissions to NuGet.org

May 22, 2018 May 22, 2018 05/22/18

Rido

In September 2017, we announced our plans to improve the security of the NuGet ecosystem by introducing the ability for package authors to sign packages. Today, we want to announce support for any NuGet.org user to submit signed packages to NuGet.org. A signed NuGet package is designed to be fully compatible with pre-existing NuGet servers ...

Organizations on NuGet.org

April 17, 2018 Apr 17, 2018 04/17/18

Anand Gaurav

We are happy to announce support for Organizations on NuGet.org. This will help businesses and open-source projects collaborate on packages using a single nuget.org identity. Why organizations? NuGet.org used to allow you to create an account and publish packages through that account with little support to manage and publish packages as a ...

Migrate to PackageReference with 3 clicks

April 9, 2018 Apr 9, 2018 04/9/18

Karan Nandwani

Last year, we introduced the option to make PackageReference the default package management format for managing NuGet dependencies when installing the first NuGet package for a newly created projects. With Visual Studio Version 15.7 Preview 3, we have introduced the capability to migrate existing projects that use the packages.config format to...

NuGet Package Identity and Trust

April 17, 2017 Apr 17, 2017 04/17/17

Daniel Jacobson

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...

NuGet is now fully integrated into MSBuild

March 16, 2017 Mar 16, 2017 03/16/17

Karan Nandwani

In the past, NuGet packages were managed in two different ways - packages.config and project.json - each with their own sets of advantages and limitations. With Visual Studio 2017 and .NET Core, we have improved the NuGet package management experience by introducing the PackageReference feature in MSBuild. PackageReference brings new and ...

Introducing scoped API keys

February 2, 2017 Feb 2, 2017 02/2/17

Anand Gaurav

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 ContentFiles Demystified

January 26, 2016 Jan 26, 2016 01/26/16

Jeffrey Fritz

Updated - Feb 26, 2015: Thanks to Jared Barneck for some suggested edits to add some steps to the sample NuGet creation process In NuGet 3.3, the contentFiles feature was introduced to support project.json managed projects and packages that are indirectly referenced in a project. This was an important change because it brings the ability to ...

Accelerate your NuGet.Server

January 13, 2016 Jan 13, 2016 01/13/16

Maarten Balliauw

Since its inception, NuGet supports setting up custom package sources. There's the default NuGet Gallery, there's third-party NuGet hosting (see the NuGet Ecosystem), we can use local directories on our hard drive or a network UNC share (like \yourserver\nuget) and there's the NuGet.Server package that we can use to create our own NuGet ...

Meet the new NuGet status page

September 28, 2015 Sep 28, 2015 09/28/15

Maarten Balliauw

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 ...

The NuGet Blog