NuGet 5.9 is one of many releases in our .NET unification journey. Our NuGet tooling helps developers discover new .NET packages to use for their .NET applications, while making package management easier during your daily development.<\/p>\n
NuGet 5.9 Highlights<\/h2>\n
There are many important improvements in NuGet 5.9<\/a>:<\/p>\n We heard that there were challenges when specifying floating versions<\/a> in your projects, and you will now see the requested version and what version was ultimately resolved. We hope this improves your experience using floating version notation with NuGet.<\/p>\n One challenge we\u2019ve heard from you is knowing where your package is coming from & the specific contents of that package. Fear not, we\u2019ve now added additional improvements into the global package folder<\/a> & installation logs so you can check exactly what package source & content hash was restored by NuGet.<\/p>\n You can now view this information in the contents of the respective .nupkg.metadata<\/strong> file of the package you\u2019re interested in.<\/p>\n Additionally, when installing a package, you\u2019ll see the same information to ensure the right package was restored at install time.<\/p>\n We heard that you wanted the ability to quickly update packages within the solution explorer. In this release, you can now right click on package(s) you’d like to update.<\/p>\n This will then automatically select the packages in the package manager for you to update.<\/p>\n In NuGet 5.9 & Visual Studio 2019 16.9, we have continued to improve the performance of managing your project\u2019s packages. Here is a small list of the improvements we\u2019ve made so far that was benchmarked against the OrchardCore<\/a> project that contains over 150 projects, and what you can expect soon.<\/p>\n We believe with these changes, that managing your dependencies in Visual Studio will be faster than ever and we\u2019re excited for you to try them out by updating to the latest version of Visual Studio.<\/p>\n We\u2019ve heard that a number of icon choices in Visual Studio didn\u2019t quite make sense to you. In this release, we\u2019ve improved a number of different areas.<\/p>\n First, we\u2019ve changed the \u201cManage NuGet Packages\u2026\u201d context menu to have an official NuGet icon.<\/p>\n Next, when a package is on the latest version, many users found a down-arrow to be confusing as to whether an update is available, so we reverted a change to bring back the old green checkmark confirming you\u2019re on the latest version of the package.<\/p>\n Finally, we improved the experience of deprecation icons to be a bit more reliable & appear where you need to see them the most.<\/p>\n NuGet 5.9 includes support for .NET 5, and therefore requires you to be using the same minor version of tooling.<\/p>\n It is advised to ensure that you are on the same version of tooling in your environments. Visual Studio 16.9, MSBuild 16.9, and .NET 5.0 require NuGet 5.9 or later.<\/strong><\/p>\n One such way of ensuring you have the same version of tooling being used in your environments is to use MSBuild, Visual Studio, or the dotnet CLI. You can get started with NuGet restore in each of these scenarios in the following way:<\/p>\n NuGet 5.9 is a great release that brings a refined experience to everything package management. We\u2019ve added a bunch of exciting quality of life improvements while also bringing you a more performant package management experience.<\/p>\n We\u2019re excited to see you use NuGet 5.9 & include it in your toolset to build amazing things with .NET.<\/p>\n For more details on NuGet 5.9, see our official release notes<\/a>.<\/p>\n Your feedback is important to us. If there are any problems with this release, check our GitHub Issues<\/a> and Visual Studio Developer Community<\/a> for existing issues. For new issues within NuGet, please report a GitHub Issue<\/a>. For general NuGet experience issues, let us know via the Report a Problem<\/a> option found in your favorite IDE under Help > Report a Problem.<\/strong><\/p>\n Additionally, to see what is coming next to NuGet, view our public proposals<\/a> or create your own proposal<\/a>. Be sure to leave your feedback on existing issues & pull requests!<\/p>\n","protected":false},"excerpt":{"rendered":" NuGet 5.9 is a great release that brings a refined experience to everything package management. We\u2019ve added a bunch of exciting quality of life improvements while also bringing you a more performant package management experience.<\/p>\n We\u2019re excited to see you use NuGet 5.9 & include it in your toolset to build amazing things with .NET.<\/p>\n","protected":false},"author":551,"featured_media":1801,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[7874,7930],"tags":[104,7957,7958],"class_list":["post-1939","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nuget","category-release-announcement","tag-nuget","tag-nuget-5-9","tag-visual-studio-16-9"],"acf":[],"blog_post_summary":" NuGet 5.9 is a great release that brings a refined experience to everything package management. We\u2019ve added a bunch of exciting quality of life improvements while also bringing you a more performant package management experience.<\/p>\n We\u2019re excited to see you use NuGet 5.9 & include it in your toolset to build amazing things with .NET.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/1939","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/551"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=1939"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/1939\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/1801"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=1939"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=1939"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=1939"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Floating Versions in Solution-Level Package Manager<\/h2>\n
![\"Requested](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/floatingversion-1.png\")
<\/p>\nContent Hash & Source Details for Packages<\/h2>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/metadata-1.png\")
<\/p>\n![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/installlog-1.png\")
<\/p>\nUpdate Package Context Menu Action<\/h2>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/update1-1.png\")
<\/p>\n![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/update2-1.png\")
<\/p>\nVisual Studio Package Manager Improvements<\/h2>\n
\n
New & Polished Icons in Package Manager<\/h2>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/managenugetpackages-1.png\")
<\/p>\n![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/greencheck-1.png\")
<\/p>\n![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2021\/03\/deprecated-1.png\")
<\/p>\nKnown Issues<\/h2>\n
\n
Closing<\/h2>\n
Feedback<\/h2>\n