![]() Your subscription will be upgraded to Visual Studio Enterprise with MSDN. TIP: Buy or Renew Visual Studio 2013 PREMIUM with MSDN now and be automatically upgraded to Visual Studio 2015 ENTERPRISE with MSDN when Visual Studio 2015 is released. Windows 8.1 (64-bit) in VMWare Fusion 6.0.Your Visual Studio Professional with MSDN subscription will continue without change ![]() dll is currently marked "could not be found". That said, there might be an intentional reason that the 2.x package manager behaves differently and refuses to remove the Reference element if. In fact based on my quick tests, it appears that NuGet Package Manager 3.0.0 in VS 2015 does ignore the "found" status, so this issue does not affect VS 2015 RTM. dll is marked as "could not be found" when uninstalling the package. Maybe the package manager could ignore the fact that the. Maybe the NuGet Package Manager could "imitate" the manual workaround and tell Visual Studio to refresh the status of the assembly references after the "Restore" process at step 3?ī. Visual Studio will now see the "Newtonsoft.Json" assembly correctly, the "could not be found" warning will disappear from the Error List, and the package update at step 6 will produce the correct Version= specifier. (Note: this issue is not specific to the "Newtonsoft.Json" package.) WorkaroundĪfter restoring the package at step 3, select the "PortableClassLibrary1" project in the Solution Explorer and then click the "Refresh" button at the top of the Solution Explorer. If this reference is required by your code, you may get compilation errors. Check to make sure the assembly exists on disk. Could not locate the assembly "Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed, processorArchitecture=MSIL". Warning 1 Could not resolve this reference. If you attempt to build the project after step 6, you will see a similar, more verbose warning: Warning 1 The referenced component 'Newtonsoft.Json' could not be found. The package manager apparently skips over this reference because Visual Studio reports that it cannot be found: The primary problem seems to be that when the NuGet Package Manager uninstalls the 6.0.8 version of "Newtonsoft.Json", it does not remove the original reference to "". (Note: to make the test case I started with a new "Visual C# -> Class Library (Portable)" solution, ran "Install-Package Newtonsoft.Json -Version 6.0.8", and then intentionally deleted the packages folder.) ResultsĪfter step 6, PortableClassLibrary1.csproj contains an incorrect Version= specifier for the "Newtonsoft.Json" assembly: Click the "Update" button on the right side of the "Json.NET" NuGet package. ![]() If the "Updates" heading is already selected, click the "Installed Packages" heading on the left of the package manager window.Click the "Restore" button at the top right of the package manager window.Open "Tools -> NuGet Package Manager -> Manage NuGet Package for Solution".Download and unzip the test case, and then open the.Regression status: probably not a regressionĬertainly not an immediate regression: 0.756 and 3.765 have the same behavior Steps to reproduce So if nothing else, this report can serve as some small documentation. I suspect this might be an old known issue that has an acceptably low impact to be left as-is, but I searched for the associated warning message in both the GitHub issues and the old CodePlex issues, and I didn't notice a previous report. This issue does not affect NuGet Package Manager 3.0.0 in VS 2015. When uninstalling packages in Visual Studio 2013 the NuGet Package Manager does not remove references that are currently marked "could not be found".
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |