Hi,
I noticed NuGet extension wasn't loaded in VS2010. Initially I didn't pay much attention to it. But then today I restarted VS2010 and it popped up an error stating:
The 'NuGet'.Tools.NuGetVSEventsPackage.NuGet.Tools, Version=2.8.50126.400, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a' package did not load correctly.
The second paragraph of the error suggested starting VS with /log and then examining the log file for error details.
I did that however, I don't see good error details in the log for me to figure out the cause of the problem.
I believe the last update I did was to update to NCrunch 3.3.06.
While I'm not 100% certain I'm wondering if the update to 3.3.06 caused some problem with NuGet loading during VS startup.
I can send ActivityLog.xml if needed.
Remco NCrunch Developer
#9768
01 Feb 2017 22:03 UTC
Hi,
Under VS2010, an upgrade of NCrunch (or any extension) causes VS to flush its package cache and rebuild this.
Because VS is not perfect, there are some situations where clearing out and rebuilding the cache can cause internal problems. This means that while it is unlikely NCrunch is responsible for a plugin clash, the installation may have triggered an unrelated problem.
I recommend trying the following command: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /setup
This will rebuild VS2010's extension cache and configuration.
You can also try: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /rootsuffix test
This will start VS2010 with a different registry hive. If the VS registry hive is corrupt, this will work around the problem.
In all truth, without solid indication that NCrunch is at fault here, it will be very hard for me to investigate this problem as all symptoms are pointing inside VS itself.
Under VS2010, an upgrade of NCrunch (or any extension) causes VS to flush its package cache and rebuild this.
Because VS is not perfect, there are some situations where clearing out and rebuilding the cache can cause internal problems. This means that while it is unlikely NCrunch is responsible for a plugin clash, the installation may have triggered an unrelated problem.
I recommend trying the following command: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /setup
This will rebuild VS2010's extension cache and configuration.
You can also try: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /rootsuffix test
This will start VS2010 with a different registry hive. If the VS registry hive is corrupt, this will work around the problem.
In all truth, without solid indication that NCrunch is at fault here, it will be very hard for me to investigate this problem as all symptoms are pointing inside VS itself.
Hi Remco,
Thanks for the reply. I tried both of your suggestions and they didn't fix the problem.
I re-installed NuGet Package Manager using these instructions:
https://github.com/paypal/sdk-core-dotnet/wiki/Using-Nuget-in-Visual-Studio-2010-&-2012
That fixed the problem. I probably didn't need to try your two suggestions.
As always: I love using your fantastic tool!
Thanks, Ed
Thanks for the reply. I tried both of your suggestions and they didn't fix the problem.
I re-installed NuGet Package Manager using these instructions:
https://github.com/paypal/sdk-core-dotnet/wiki/Using-Nuget-in-Visual-Studio-2010-&-2012
That fixed the problem. I probably didn't need to try your two suggestions.
As always: I love using your fantastic tool!
Thanks, Ed
Post a reply
Log in to reply.