The NuGet Blog

The latest news, updates, and insights from the NuGet team

Package Manifests

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

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

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

Support for Native Projects

In the NuGet 2.5 release notes, we called out that NuGet now has support for native projects. We wanted to explain exactly what "support for native projects" means. Visual Studio Support Until NuGet 2.5, if you were working in a Visual C++ project, the 'Manage NuGet Packages' context menu would not show up for the project; with NuGet 2.5, we...

XDT web.config transforms

Sitting there since October 12, 2010, with a total of 55 votes accumulated since then, there's a NuGet feature that has had more than its fair share of attention: Support Visual Studio (XDT) Web.config Transforms. It's the 17th highest voted work item of all time for NuGet, and the 5th highest voted open work item. Today, we are announcing ...

Feedback usabilla icon