Announcing NuGet 3.5 RC

NuGet 3.5 RC for Visual Studio 2015 and nuget.exe provide quality improvements, performance improvements, features and new target frameworks like netstandard and netcoreapp.

Downloads

All NuGet downloads are available on http://nuget.org/downloads.

New Features

Support for new Target Frameworks

.NET Standard and Net Core App TFM support is now available in 3.5 RC and 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 to support a new PackageType property in the nuspec. This property allows 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. Packages.config scenarios allowed a package to define a required min version of client it can work with. This now works in project.json scenarios as well. 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.

Performance Improvements

The key scenarios we have improved are Restore, Package Manager Console Load and Update performance.

  • Restore times in portable apps deployed through Kudu have reduced from over 15 secs to 3 secs.

  • Package Manager Console Load in large solutions are now much faster. In one of our sample projects it reduced from over 132s to 10s.

  • Package Updates in Visual Studio with ReSharper installed has been significantly improved. In our tests we have seen it drop from over 140 secs to 68 secs. We working together with the resharper team on further improvements that require code changes on both sides.

Release Notes

3.5 RC

Issues List

3.5 RC

What’s Next

The team is now shifting gears into transitioning .NET CLI from project.json into MSBuild and and further investments 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.

Published August 11, 2016 by Harikrishna Menon

blog comments powered by Disqus