Loading a project in Visual Studio 2015 with Update 2 (either automatically when VS start or manual load), I receive an error saying: 'The Scc Display Information package did not load correctly'.
The ActivityLog has:
<entry>
<record>541</record>
<time>2016/04/01 13:43:26.048</time>
<type>Error</type>
<source>VisualStudio</source>
<description>SetSite failed for package [Scc Display Information][An item with the same key has already been added.]:{ at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)
 at Microsoft.VisualStudio.Services.VsTask.GetResult()}</description>
<guid>{D7BB9305-5804-4F92-9CFE-119F4CB0563B}</guid>
<hr>80070057 - E_INVALIDARG</hr>
<errorinfo></errorinfo>
</entry>
<entry>
<record>542</record>
<time>2016/04/01 13:43:26.050</time>
<type>Error</type>
<source>VisualStudio</source>
<description>End package load [Scc Display Information]</description>
<guid>{D7BB9305-5804-4F92-9CFE-119F4CB0563B}</guid>
<hr>80070057 - E_INVALIDARG</hr>
<errorinfo></errorinfo>
</entry>
I installed VS2015 with Update 2 over VS2015 with Update 1. I got the error (package ... did no load correctly).
I uninstalled VS2015 completely. I reinstalled VS2015 with Update 2 completely. I still have the same problem about 'The Scc Display Information' package did not load correctly'.
Update The problem seems similar to the same problem I had with VS2015 Update 1. But I think it is not related to NuGet because I have no package with "Scc" in it. I always associated "Scc" with Visual Source Safe (could it be related ?). I suspect the problem come from the registry but I can't figure out where.
I tried both solutions from this Stack Overflow link without success:
Any idea how to fix this?
This is caused if you have certain MSSCCI-based SCC providers installed. You can check your registry's HKLM key: SOFTWARE\WOW6432Node\SourceCodeControlProvider
If this key is present, that's likely causing the problem.
Install the fix from KB3151378.
New installations of VS 2015 Update 2 after 4/11/2016 automatically include this fix and no manual installation of a fix is necessary.
If you don't use any of the SCC providers mentioned there, try renaming the key to SourceCodeControlProvider_
(added underscore). The package should then load cleanly.
We're working on shipping a fix for VS2015 Update 2 to resolve the issue even while you have MSSCCI-based SCC providers installed.
(Microsoft Employee)