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 use PackageReference instead.
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.
Today, we would like to introduce you to the NuGet Beta Channel for the Visual Studio 2015 NuGet Package Manager. In the last 2 months, we have been focusing on improving the quality of the package management experience in Visual Studio 2015 and we have released over 3 consecutive versions of the package manager with added features,
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.
As NuGet continues to gain momentum, more Microsoft teams have been seeking to install NuGet packages from their Visual Studio tooling. This began with ASP.NET, where NuGet was born, when project templates started coming with pre-installed NuGet packages. More recently, we’ve heard of teams all across Microsoft with tooling gestures that result in NuGet packages being installed.
As we work on some big changes for NuGet 3.x, we’re finding that we’re at a crossroads: Should we use .NET 4.5 and improve our Visual Studio UI using new features available in Visual Studio 2012, Visual Studio 2013, and Visual Studio “14”;
While working on NuGet 2.8, we addressed some bugs dealing with the “Update All” behavior, where a single gesture will update all packages in the project. During the testing of those fixes, another bug was filed stating, After using Update All,
There has been reports that VS hangs when Manage NuGet Packages for Solution menu item is clicked. When VS responds again, it reports the following error:
“Loading the projects is required to complete the requested action. If you click the Cancel button,
Recently there have been customer reports of hangs in Visual Studio while installing or updating NuGet packages. It could be related to this issue, if you have ReSharper 8.1 EAP installed.
The solution is to update ReSharper to one of the stable versions such as ReSharper 8.1.
When NuGet 2.0 released, it included the requirement that in order to use package restore, you first needed to explicitly provide consent to the NuGet client to download packages over the Internet. This requirement added some friction to normal developer workflows,