The NuGet team is happy to introduce version 3.4 and 3.4.1 of the NuGet clients for Visual Studio 2015. We shipped v3.4 with Visual Studio 2015 Update 2 and immediately followed that with the 3.4.1 release to address a small set of issues that were identified after Visual Studio bundled the NuGet 3.4 release.
Post by this author
After several months of measuring, tuning, and testing, the NuGet team would like to announce version 3.4 RC of the NuGet clients for Visual Studio 2015 and the command-line. There were three main areas that the team focused on for this version:
Improved Performance in Visual Studio
Minor user-interface improvements
We think you’ll find these updates a welcome change that improves your day-to-day interactions with NuGet packages.
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.
A question that comes up from time to time is: how does Visual Studio 2015 add references when using project.json files in conjunction with a csproj without modifying the csproj file? This is a good question and demonstrates some of our strategy to help make NuGet easier to integrate into project systems without having to teach NuGet how to work with every project system.
Big news: a new version of the NuGet clients has been released! This is version 3.3 of the client, with a new command-line and Visual Studio 2015 extension available for use. Use the above links to download from the NuGet distribution site,
We want to continue our discussion of the recent changes made to the NuGet experience with the v3 releases, and in this second blog post of the series we are going to focus on the user interface updates that were made for Visual Studio 2015.
Today we are releasing nuget.exe 3.2.1-RC and NuGet 2.9-RC. A number of issues were identified in both versions that prevented interoperability on Linux and OSX operating systems. We also made some fixes to 3.2 in order to reduce network utilization.
Below are the top highlights of these releases
Now skipping interpreting nuspec documents that are not well formed
Corrected an issue that prevented the NuGet extension from loading properly in Visual Studio 2013 Express
Improved handling the /r/n characters during network communication from a non-Windows operating system
The complete 2.9 issue list is available in GitHub
Corrected the casing of the NuGet.Config file being read.
Since Visual Studio 2015 was released in July, developers have started using a new version of NuGet, NuGet 3 We decided to introduce a number of significant changes based on feedback from the community. With any major version change, some things break… and usually for a good reason.
The NuGet community is awesome; involved and eager to build software to make it easy for use in bigger projects that the components and libraries that they themselves are building. Every now and again, community members can get a little too eager.
Today we are publishing the version 3.2 updates to the NuGet clients. We took customer feedback regarding issues and feature direction and assembled this release to address those immediate concerns. There are fixes available for a number of blocking issues and adds support for push and list for compliant V3 servers.