The latest news, updates, and insights from the NuGet team
February 1, 2018Feb 1, 201802/1/18In December 2017, we changed the NuGet.org backend publishing pipeline to introduce a set of validation steps for submitted packages. Our goal is to maintain the same level of experience in terms of the time and effort it would take to publish a package and have it available for download.
September 14, 2017Sep 14, 201709/14/17In our NuGet Fall 2017 Roadmap, we highlighted security as the main area of investment over the next few months. This blog post describes a major part of that roadmap in greater detail – package signing.
We started talking about supporting signed packages on NuGet.org a while ago.
September 7, 2017Sep 7, 201709/7/17NuGet.org, the package manager for .NET, was purpose-built as a global service with high scale performance regardless of the developer’s location. We are finding that this is not always the case, particularly for developers accessing the service from China, which is the second largest region for .NET developers.
August 15, 2017Aug 15, 201708/15/17We are happy to announce an update to the NuGet client that comes bundled with Visual Studio 2017 version 15.3 RTW and .NET Core 2.0 SDK. This release introduces support for new scenarios such as .NET Core 2.0/.NET Standard 2.0, some new features,
August 9, 2017Aug 9, 201708/9/17Over the past 6 months, the NuGet team has been working hard to ensure the growth of the .NET ecosystem. NuGet has grown significantly during this timeframe: NuGet.org is closing in on 4 billion packages served (up from a billion packages just a year ago),
July 18, 2017Jul 18, 201707/18/17It’s been a long time coming, and today we are excited to announce some big changes coming to NuGet.org. With almost 3 million monthly page views, NuGet.org is the gateway for .NET developers to find packages that accelerate their projects. However,
April 17, 2017Apr 17, 201704/17/17Update on 10/16/2017: Package ID Prefix Reservation is now live. The documentation can be found here.
We want to start this post with a huge thanks to you, the NuGet community. Over the last several months we have been talking to many of you to get feedback on NuGet package identity and trust.
March 16, 2017Mar 16, 201703/16/17In 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.
February 2, 2017Feb 2, 201702/2/17Update 2/14 (05:00 PM PST): This feature is now live! Login to your nuget account and expand the API Keys section to see the new experience.
Since last year, we have been working on several fronts to advance NuGet as a secure environment for package distribution.
January 19, 2017Jan 19, 201701/19/17At NuGet, we are constantly improving our security. One of the steps we are taking is to move our HTTPS end points to meet industry standards for algorithms and protocols. This means that connecting to nuget.org services from machines that don’t support modern cipher algorithms will no longer be supported (such as TLS 1.0 support in Windows XP).
Debugging
November 16, 2018Nov 16, 201811/16/18Starting today, you can publish symbol packages to the NuGet.org symbol server. With NuGet.org as a single service provider for libraries and symbols, package authors and consumers will have a streamlined publishing and consumption experience. With a single place for managing authentication and identity,
May 1, 2018May 1, 201805/1/18We are excited to welcome SymbolSource.org to the .NET Foundation! SymbolSource has been providing a valuable service to the .NET Community for years with the ability to host Symbols for public NuGet packages on SymbolSource. With recent progress made in several areas,
Feature Announcement
September 30, 2019Sep 30, 201909/30/19We are excited to announce that nuget.org now supports package deprecation. This has been a long standing ask that will help the ecosystem use supported packages. As a package publisher on nuget.org, you can now deprecate packages that are obsolete, legacy,
August 22, 2019Aug 22, 201908/22/19It’s been a long time coming, and today we are excited to announce the new and improved search on NuGet.org leveraging Azure Search. We want to start this post with a huge thanks to you, the NuGet community, for providing feedback.
July 17, 2019Jul 17, 201907/17/19There are several criteria you can use today to evaluate NuGet packages. We received feedback that you would like even more information to help choose the right packages. We’re excited to introduce GitHub Usage on nuget.org, which allows you to explore top GitHub repositories that depend on the package you are looking at.
December 17, 2018Dec 17, 201812/17/18With PackageReference, NuGet always tries to produce the same closure of package dependencies if the input package reference list has not changed. However, there are a few scenarios where it may not be able to do so. While these cases are limited,
November 16, 2018Nov 16, 201811/16/18Starting today, you can publish symbol packages to the NuGet.org symbol server. With NuGet.org as a single service provider for libraries and symbols, package authors and consumers will have a streamlined publishing and consumption experience. With a single place for managing authentication and identity,
August 27, 2018Aug 27, 201808/27/18NuGet.org now supports surfacing source code repository link for NuGet packages. This will enable package authors to surface both the project’s website and the source repository using the projectUrl and the repository properties respectively instead of having to choose between the two using just the projectUrl property.
May 22, 2018May 22, 201805/22/18In September 2017, we announced our plans to improve the security of the NuGet ecosystem by introducing the ability for package authors to sign packages. Today, we want to announce support for any NuGet.org user to submit signed packages to NuGet.org.
April 17, 2018Apr 17, 201804/17/18We are happy to announce support for Organizations on NuGet.org. This will help businesses and open-source projects collaborate on packages using a single nuget.org identity.
Why organizations?
NuGet.org used to allow you to create an account and publish packages through that account with little support to manage and publish packages as a team or a group.
April 9, 2018Apr 9, 201804/9/18Last 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.
April 17, 2017Apr 17, 201704/17/17Update on 10/16/2017: Package ID Prefix Reservation is now live. The documentation can be found here.
We want to start this post with a huge thanks to you, the NuGet community. Over the last several months we have been talking to many of you to get feedback on NuGet package identity and trust.
Incident
March 22, 2018Mar 22, 201803/22/18We did this blog post to report about the incident that happened on March 22, 2018. In the last couple of days we digged deeper into the incident. Here is the summary of our findings and proposed next steps.
Customer Impact
NuGet.org website and V2 APIs were unavailable for 2 hours on March 22,
September 10, 2013Sep 10, 201309/10/13Starting September 3rd, some users started having issues uploading packages that contain portable libraries; on September 10th, we deployed a fix to address those issues.
Errors Experienced
Depending on how you were publishing your package, you would have experienced the errors in a few different ways.
August 29, 2013Aug 29, 201308/29/13After NuGet 2.7 was released with Automatic Package Restore and implicit consent, some users reported that they were still seeing build errors indicating that package restore consent had not been given. When we made the package restore changes in NuGet 2.7,
April 4, 2013Apr 4, 201304/4/13On March 6th 2013, nuget.org’s package download was broken for one and a half hours. Some outages involve factors beyond our control; this time it was very much our own fault and we would like to apologize. We also want to openly discuss the outage and reassure you that we are working on preventing reoccurences.
August 24, 2012Aug 24, 201208/24/12As you might know, NuGet has been having some performance (and timeout) related issues recently. Earlier this week, we completed a deployment that helped, but it didn’t address everything.
Many users are still seeing slow responses or even timeouts when trying to use the ‘Manage NuGet Packages’
August 22, 2012Aug 22, 201208/22/12Earlier this evening, we announced that the NuGet Gallery would be offline for about an hour during a scheduled upgrade. That upgrade is now complete.
We expect this deployment to help address performance issues we’ve been experiencing for the past week.
August 22, 2012Aug 22, 201208/22/12As mentioned in the previous post, we’ve been working to address some performance problems on the NuGet Gallery.
The fixes we have in place include some time-consuming database migrations. During our dry run deployments, we found that virtually all requests to the database will time out while these migrations are running.
August 22, 2012Aug 22, 201208/22/12Since August 16th, and especially since August 21st, the NuGet Gallery has been exhbiting intermittent performance issues. Some users are reporting errors when attempting to browse or search for NuGet packages from Visual Studio or other clients. Many users are reporting that browsing and searching are slow.
March 14, 2012Mar 14, 201203/14/12The NuGet Gallery was unavailable on March 9th from approximately midnight until 7:52 A.M., nearly eight hours. During this time all HTTP requests to the gallery website failed. In addition to affecting website users, the outage affected all NuGet client programs (such as the Visual Studio extension and nuget.exe) and other software that relies on the NuGet Gallery’s feed and API.
Insights
May 19, 2016May 19, 201605/19/16A few weeks back, we deployed our consolidated REST API powering NuGet.org and the NuGet client experience in Visual Studio. An invisible change for our users, but a big change for the NuGet team. This consolidated REST API lays the foundation of our future work on the server side of NuGet.
May 10, 2016May 10, 201605/10/16Today, NuGet.org reached one billion downloads. This is a momentous achievement for our users and the community of package authors who continue to use and build new libraries that is the cornerstone of .NET adoption. We want to take this opportunity to give a huge thank you to the millions of our users who made this milestone possible.
September 22, 2015Sep 22, 201509/22/15This is a guest blog, by Andrew Arnott from the Visual Studio team. Andrew was having performance issues with NuGet updating or installing packages from a UNC share. These issues where well known, and our solution in the past was to point people to http servers.
September 20, 2013Sep 20, 201309/20/13Starting with NuGet 2.6, XML-Document-Transform (XDT) is supported to transform XML files inside a project. The XDT syntax can be utilized in the .install.xdt and .uninstall.xdt file(s) under the package’s Content folder, which will be applied during package installation and uninstallation time,
December 31, 2012Dec 31, 201212/31/12Among the supported commands in NuGet’s Package Manager Console, Update-Package is arguably the most powerful in terms of its supported parameters and switches. The primary purpose of the command is to update package(s) in your projects to a higher (possibly latest) version.
October 23, 2012Oct 23, 201210/23/12When you build your NuGet packages using nuget.exe, you may have noticed that sometimes you get a warning about the created package. Here’s one example:
This warning is generated by one of NuGet’s package analysis rules. Think of these as the NuGet equivalent of an FxCop rule.
NuGet
February 18, 2020Feb 18, 202002/18/20Last November, we shared our two-stage plan for deprecating TLS 1.0/1.1 on NuGet.org and actions you can take today to ensure your systems use TLS 1.2. In this post, we will go into more details and a specific timeline for Stage 1 i.e.
NuGet.org
February 18, 2020Feb 18, 202002/18/20Last November, we shared our two-stage plan for deprecating TLS 1.0/1.1 on NuGet.org and actions you can take today to ensure your systems use TLS 1.2. In this post, we will go into more details and a specific timeline for Stage 1 i.e.
November 15, 2019Nov 15, 201911/15/19co-authored by Scott Bommarito
At Microsoft, using the latest and secure encryption techniques is very important to us to ensure the security and privacy of our customers. TLS 1.0 and TLS 1.1, released in 1999 and 2006 respectively, are known to be vulnerable to a number of attacks including POODLE and BEAST.
September 30, 2019Sep 30, 201909/30/19We are excited to announce that nuget.org now supports package deprecation. This has been a long standing ask that will help the ecosystem use supported packages. As a package publisher on nuget.org, you can now deprecate packages that are obsolete, legacy,
August 22, 2019Aug 22, 201908/22/19It’s been a long time coming, and today we are excited to announce the new and improved search on NuGet.org leveraging Azure Search. We want to start this post with a huge thanks to you, the NuGet community, for providing feedback.
July 17, 2019Jul 17, 201907/17/19There are several criteria you can use today to evaluate NuGet packages. We received feedback that you would like even more information to help choose the right packages. We’re excited to introduce GitHub Usage on nuget.org, which allows you to explore top GitHub repositories that depend on the package you are looking at.
August 27, 2018Aug 27, 201808/27/18NuGet.org now supports surfacing source code repository link for NuGet packages. This will enable package authors to surface both the project’s website and the source repository using the projectUrl and the repository properties respectively instead of having to choose between the two using just the projectUrl property.
August 10, 2018Aug 10, 201808/10/18In May, we implemented Stage 1 and enabled support for any NuGet.org user to submit signed packages to NuGet.org. Today, we are announcing Stage 2 of our NuGet package signing journey – tamper proofing the entire package dependency graph.
What is a Repository Signature?
May 22, 2018May 22, 201805/22/18In September 2017, we announced our plans to improve the security of the NuGet ecosystem by introducing the ability for package authors to sign packages. Today, we want to announce support for any NuGet.org user to submit signed packages to NuGet.org.
May 15, 2018May 15, 201805/15/18We had previously announced the deprecation of NuGet.org’s home-grown authentication in favor of Microsoft accounts (MSA) that will allow us to add support for additional security systems such as two-factor authentication (2FA). We will be disabling the NuGet.org’s home-grown authentication mechanism starting June 1st,
April 17, 2018Apr 17, 201804/17/18We are happy to announce support for Organizations on NuGet.org. This will help businesses and open-source projects collaborate on packages using a single nuget.org identity.
Why organizations?
NuGet.org used to allow you to create an account and publish packages through that account with little support to manage and publish packages as a team or a group.
Other announcements
November 15, 2019Nov 15, 201911/15/19co-authored by Scott Bommarito
At Microsoft, using the latest and secure encryption techniques is very important to us to ensure the security and privacy of our customers. TLS 1.0 and TLS 1.1, released in 1999 and 2006 respectively, are known to be vulnerable to a number of attacks including POODLE and BEAST.
January 12, 2017Jan 12, 201701/12/17In late 2016, we started on the journey of improving the docs experience for NuGet with the revamped docs experience. Continuing that journey, today we are announcing the move to docs.microsoft.com/nuget. Given how NuGet has grown to become an integral part of the Visual Studio and .NET ecosystems,
September 20, 2016Sep 20, 201609/20/16Last month, we launched a preview of the revamped Nuget docs experience. We made a number of improvements:
New quick-starts for creating and consuming packages.
End to end guides for new platforms such as .NET Standard and UWP.
A simpler and more intuitive organization of topics.
August 22, 2016Aug 22, 201608/22/16Update 9/20 (11:00 A.M PST): The revamped NuGet Docs experience is now live on docs.nuget.org. Read more about it here – New experience for NuGet Documentation
docs.nuget.org is the authoritative guide on everything NuGet. It is used as reference by nearly 180k developers with over 500k page views a month.
January 19, 2016Jan 19, 201601/19/16A 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.
October 7, 2015Oct 7, 201510/7/15The 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.
August 11, 2015Aug 11, 201508/11/15In the last few months we have constantly moved the issues and all new code base to GitHub. Today we moved the last bits of code from CodePlex to GitHub. We have stopped monitoring the CodePlex site completely, and will not be taking further looks at reports there or pull requests.
December 3, 2014Dec 3, 201412/3/14You’ve probably seen the cool announcements from Microsoft about the new Community Edition of Visual Studio and the upcoming Visual Studio 2015 release in the new year. We at the NuGet team have been ramping up our tools to support the new Visual Studio with a better visual experience and a better command-line experience.
October 1, 2014Oct 1, 201410/1/14Have you ever seen this error before?
Doesn’t it make you want to yell and scream at NuGet, “Why did you just show it to me if I couldn’t install it!?‽”
Yeah, it makes us want to yell and scream too,
May 8, 2014May 8, 201405/8/14Blog Redesign is LIVE!
What better way to announce upcoming website redesigns than by implementing that redesign on our blog? Earlier today, we deployed changes to http://blog.nuget.org that apply a new visual design that we expect to carry over to the docs and gallery sites too.
Release announcement
August 15, 2017Aug 15, 201708/15/17We are happy to announce an update to the NuGet client that comes bundled with Visual Studio 2017 version 15.3 RTW and .NET Core 2.0 SDK. This release introduces support for new scenarios such as .NET Core 2.0/.NET Standard 2.0, some new features,
December 21, 2016Dec 21, 201612/21/16Today we are releasing an update to the NuGet.Server package. The purpose of this update is to address a bug that enabled NuGet.Server to be installed on projects that target .NET Framework versions less than 4.6.
Issue addressed
Previously, there was a bug in NuGet.Server 2.11.2 (3257,
November 21, 2016Nov 21, 201611/21/16NuGet 4.0 RC for Visual Studio 2017 is focused on adding support for .NET Core scenarios, addressing key customer feedback and improving performance in a variety of scenarios. This release brings several improvements like support for PackageReference, NuGet commands as MSBuild targets,
October 27, 2016Oct 27, 201610/27/16NuGet 3.5 RTM 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 https://nuget.org/downloads. NuGet.exe 3.5 RTM is not marked as the latest yet in the download page or uploaded as a package,
August 11, 2016Aug 11, 201608/11/16NuGet 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.
April 22, 2016Apr 22, 201604/22/16Today, we are releasing the 3.4.3 RTM version of the NuGet Visual Studio 2015 extension and the Windows x86 commandline executable. We continue to heavily invest in improving the quality of NuGet scenarios in Visual Studio and commandline. The complete list of issues fixed in this version is available on GitHub.
April 9, 2016Apr 9, 201604/9/16We have listened to the feedback from the community, and we have tried our very best to turn around quickly and address this feedback. Our primary focus for 3.4.2 have been around improving the quality and performance of the product.
The complete list of issues fixed in this version is available on GitHub.
March 30, 2016Mar 30, 201603/30/16The 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.
March 8, 2016Mar 8, 201603/8/16After 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:
Cross-Platform support
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.
November 18, 2015Nov 18, 201511/18/15Big 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,
Roadmap
April 10, 2019Apr 10, 201904/10/19We published our last NuGet roadmap in June last year. Many of the features announced were major additions to NuGet and we have been hard at work to implement those over the last few months. In this post, we will start by summarizing the features we have completed and then peek into the next wave of work planned.
July 2, 2018Jul 2, 201807/2/18This blog post provides insights into the NuGet team plans for the upcoming quarter (July – Sep 2018). In the March 2018 NuGet Spring 2018 Roadmap, we had outlined Package Signing, Organizations, Cross-platform credential provider support, Repeatable builds for PackageReference based projects,
March 1, 2018Mar 1, 201803/1/18In August 2017, we published the NuGet Fall 2017 Roadmap where we outlined our backlog for the upcoming quarter. Since then, we’ve published specifications for these experiences on GitHub for the community to review. You have provided a ton of great feedback that has helped us ensure we deliver the right experiences.
August 9, 2017Aug 9, 201708/9/17Over the past 6 months, the NuGet team has been working hard to ensure the growth of the .NET ecosystem. NuGet has grown significantly during this timeframe: NuGet.org is closing in on 4 billion packages served (up from a billion packages just a year ago),
October 8, 2015Oct 8, 201510/8/15Since 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.
October 14, 2014Oct 14, 201410/14/14I recently declared that NuGet is “Broken By Design.” Now, that was hyperbolic; I don’t really think NuGet is broken. In fact, I’m very pleased with NuGet (and proud of it). But I wanted to make the point that NuGet’s approach both earned it success but also came at a cost.
October 10, 2014Oct 10, 201410/10/14On January 13, 2011, NuGet 1.0 was released with ASP.NET MVC 3. On June 19, 2012, NuGet 2.0 shipped in the box with all editions of Visual Studio 2012 (including the free ones). That was a little over 2 years ago,
April 24, 2014Apr 24, 201404/24/14Evolution of NuGet
At MonkeySpace 2013 last July, we revealed some of our thinking for the Evolution of NuGet. These were the ideas we had for what would become NuGet 3.x and they included the following areas:
Package Discovery
Context-sensitive enumeration and search
Statistics and reports for package authors and consumers
Editable package metadata
Package discovery and sharing through social graphs
Package Trust / Incompatibility
Organizations or team accounts
Owner reputation
Friendly license names and filters
Feeds for owners’
Security
February 18, 2020Feb 18, 202002/18/20Last November, we shared our two-stage plan for deprecating TLS 1.0/1.1 on NuGet.org and actions you can take today to ensure your systems use TLS 1.2. In this post, we will go into more details and a specific timeline for Stage 1 i.e.
November 15, 2019Nov 15, 201911/15/19co-authored by Scott Bommarito
At Microsoft, using the latest and secure encryption techniques is very important to us to ensure the security and privacy of our customers. TLS 1.0 and TLS 1.1, released in 1999 and 2006 respectively, are known to be vulnerable to a number of attacks including POODLE and BEAST.
December 5, 2018Dec 5, 201812/5/18For the past several months we have focused on various features to improve package security and trust. Around a year back, we had announced our plans on various signing functionalities that we have been implementing at a steady pace. We enabled package author signing and NuGet.org repository signing earlier this year.
August 10, 2018Aug 10, 201808/10/18In May, we implemented Stage 1 and enabled support for any NuGet.org user to submit signed packages to NuGet.org. Today, we are announcing Stage 2 of our NuGet package signing journey – tamper proofing the entire package dependency graph.
What is a Repository Signature?
May 22, 2018May 22, 201805/22/18In September 2017, we announced our plans to improve the security of the NuGet ecosystem by introducing the ability for package authors to sign packages. Today, we want to announce support for any NuGet.org user to submit signed packages to NuGet.org.
May 15, 2018May 15, 201805/15/18We had previously announced the deprecation of NuGet.org’s home-grown authentication in favor of Microsoft accounts (MSA) that will allow us to add support for additional security systems such as two-factor authentication (2FA). We will be disabling the NuGet.org’s home-grown authentication mechanism starting June 1st,
September 14, 2017Sep 14, 201709/14/17In our NuGet Fall 2017 Roadmap, we highlighted security as the main area of investment over the next few months. This blog post describes a major part of that roadmap in greater detail – package signing.
We started talking about supporting signed packages on NuGet.org a while ago.
April 17, 2017Apr 17, 201704/17/17Update on 10/16/2017: Package ID Prefix Reservation is now live. The documentation can be found here.
We want to start this post with a huge thanks to you, the NuGet community. Over the last several months we have been talking to many of you to get feedback on NuGet package identity and trust.
January 19, 2017Jan 19, 201701/19/17At NuGet, we are constantly improving our security. One of the steps we are taking is to move our HTTPS end points to meet industry standards for algorithms and protocols. This means that connecting to nuget.org services from machines that don’t support modern cipher algorithms will no longer be supported (such as TLS 1.0 support in Windows XP).
August 25, 2016Aug 25, 201608/25/16In June, we published a blog post announcing Expiring API Keys. We received a lot of great feedback from the community about it. In retrospect, we did not do a great job explaining the motivation and reasoning for this security measure to the community.
Visual Studio
September 30, 2019Sep 30, 201909/30/19We are excited to announce that nuget.org now supports package deprecation. This has been a long standing ask that will help the ecosystem use supported packages. As a package publisher on nuget.org, you can now deprecate packages that are obsolete, legacy,
April 9, 2018Apr 9, 201804/9/18Last 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.
March 16, 2017Mar 16, 201703/16/17In 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.
May 2, 2016May 2, 201605/2/16Today, 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,
October 14, 2015Oct 14, 201510/14/15We 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.
October 8, 2014Oct 8, 201410/8/14As 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.
October 2, 2014Oct 2, 201410/2/14As 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”;
December 16, 2013Dec 16, 201312/16/13While 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,
November 18, 2013Nov 18, 201311/18/13There 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,
November 7, 2013Nov 7, 201311/7/13Recently 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.
