NuGet 3.5 Beta 2 for Visual Studio 2015, nuget.exe and NuGet 2.12 RTM for Visual Studio 2013 releases provide quality improvements, performance improvements, .NET Core CLI support, and new target frameworks like netstandard and netcoreapp for our users.
Downloads
All NuGet downloads are available on http://nuget.org/downloads.
-
2.12 RTM version of the Visual Studio 2013 will be available via Tools -> Extensions and Updates
-
3.5 Beta 2 is available through the following channels.
-
The .NET CLI 3.5 Beta 2 dotnet restore command also has been updated to this version.
New Features
Support for new Target Frameworks
.NET Standard and Net Core App TFM support is now available for Visual Studio 2012 users via the 2.12 release. 3.5 Beta 2 also now supports netstandard1.6 TFM for Visual Studio 2015 users. .NET Standard provides a more concrete guarantee of binary portability to future .NET-capable platforms with an easier-to-understand platform versioning plan.
PackageType
We have started to lay the groundwork for the support for a new PackageType property in nuspec which enables package authors to classify their packages (E.g Dependencies, Tools etc..). More information on this is available in the PackageType spec here.
MinClientVersion support in project.json
Project.json now supports MinClientVersion. You can now version packages that depend on newer NuGet versions so that you can prevent users from running into issues while trying to install packages using older versions of NuGet.
Release Notes
Issues List
What’s Next
The team is now shifting gears into transitioning .NET CLI from project.json into MSBuild and investing in performance and quality of the product.
We want to hear your feedback!
We want NuGet to meet the evolving needs of our community. If you would like share your pain points and your current and future needs, use the calendly link to set up a quick 15-30 min call with us. If you would like to send us an email instead, hit us up at feedback@nuget.org.
You can also leave a comment below, and as always, if you run into any issues or have an idea, open an issue on GitHub.
0 comments