Feature Announcement Archives | Page 2 of 3

Migrate to PackageReference with 3 clicks

Karan NandwaniApril 9, 2018Apr 9, 201804/9/18

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

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

NuGet is now fully integrated into MSBuild

Karan NandwaniMarch 16, 2017Mar 16, 201703/16/17

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

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

Jeffrey FritzJanuary 26, 2016Jan 26, 201601/26/16

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

Maarten BalliauwJanuary 13, 2016Jan 13, 201601/13/16

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

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

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

Supporting Semantic Versioning 2.0.0

Jeff HandleySeptember 24, 2014Sep 24, 201409/24/14

Updated Sept. 2015: Our roadmap and requirements have changed and we have yet to implement these features as of NuGet v3.2. We are tracking this issue on GitHub. Please track this issue to follow our progress. We adopted Semantic Versioning (SemVer) in NuGet 1.6. At the time, SemVer 1.0.0 was the current version of the spec. Adopting SemVer ...

A quick note about the new MinClientVersion attribute

Luan NguyenApril 30, 2013Apr 30, 201304/30/13

In the NuGet 2.5 release, we added the MinClientVersion property to the package manifest schema to allow for a package to demand the minimum version of the NuGet client that can install it. Because this feature was added in version 2.5, older versions of NuGet won't be able to recognize it. Therefore, older clients will always refuse to ...

The NuGet Blog