Pages

Wednesday, March 5, 2014

Error when starting VS 2010: The 'Microsoft.TeamFoundation.Client.ServicesHostPackage, Microsoft.VisualStudio.TeamFoundation.TeamExplorer, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' package did not load correctly

I tried to open Visual Studio 2010, and was met with the following error message:

---------------------------
Microsoft Visual Studio
---------------------------
The 'Microsoft.TeamFoundation.Client.ServicesHostPackage, Microsoft.VisualStudio.TeamFoundation.TeamExplorer, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' package did not load correctly.



The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by running the application together with the /log parameter on the command line, and then examining the file 'C:\Users\sl\AppData\Roaming\Microsoft\VisualStudio\10.0\ActivityLog.xml'.



Continue to show this error message?
---------------------------
Yes   No   
---------------------------

The computer used to run the following software:

  • Team Foundation Server 2010 (probably with SP1)
  • Visual Studio 2010 with SP1

Since then, I've done the following:

  • Uninstalled TFS 2010 and everything related, and upgraded to TFS 2013.
  • Kept VS 2010, and installed VS 2013 side-by-side.

My problem was solved after I did the following:

  • Installed Team Explorer from the TFS 2010 disc image.
  • Reapplied VS 2010 SP1.

Monday, February 3, 2014

NuGet install fails: "Unable to read package from path '[snip].nupkg'"

In my case, this issue came almost out of nowhere. The package installation/restoration succeeded using a regular Windows account, but failed under the SYSTEM account. You've probably verified permissions and what not, so I'll get to the solution to my specific problem: The NuGet cache was corrupted.

To verify that this is the case for you, delete the "packages" folder in your solution folder, then attempt to restore/install packages again, but add the "-NoCache" argument to your command line to prevent NuGet from using the local cache. See NuGet command line reference.

Once you verify that the cache is the problem, locate the cache folder, then simply delete the folder.

Restore/Install packages once more to verify success!

NuGet cache locations

Regular user accounts

%LOCALAPPDATA%\NuGet\Cache (C:\Users\<user>\AppData\Local\NuGet\Cache)

SYSTEM account

C:\Windows\system32\config\systemprofile\AppData\Local\NuGet\Cache
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\NuGet\Cache