If they have a checked-in version of nuget.exe that is older than what is required the build fails with an actionable error message.Įxtension and Updates Dialog after installing VS 2012.4 RC2 Support for the “Microsoft and. This also addresses the issue for build servers. This enables us to explicitly indicate a NuGet update is required to consume one of our packages, and customers that aren’t consuming our packages are not forced to update. This fixes the package installation issues.Īllows package authors to specify a minimum version of NuGet. This version of NuGet includes two fixes that we believe are most relevant for our customers: RC2 brings NuGet 2.6 (which was the latest version at the time we finalized the work for RC2). Most of our packages make use of PCLs which in turn has resulted in many customers reporting bugs that they weren’t able to install our packages in their projects. Unfortunately, the NuGet 2.0 client didn’t support portable class libraries (PCL). Although the NuGet team regularly ships updated versions via the Visual Studio gallery, many of you haven’t updated your NuGet clients yet – probably because you weren’t aware that an update exists or because you didn’t see a reason to update. The RTM version of Visual Studio 2012 included a fairly old version of the NuGet client (2.0). In this blog post, I’ll summarize those improvements. With RC2, we’ve updated the NuGet support.
As Brian Harry recently announced, there will be a Visual Studio 2012 Update 4.
0 kommentar(er)
