1

Closed

Error after uninstalling 4.7.47

description

Hi, after uninstalling 4.7.47, I get this error. It looks like the package was not fully uninstalled.

Thanks.

<entry>
<record>31</record>
<time>2014/02/07 14:56:22.907</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [StyleCop.VisualStudio.StyleCopVSPackage, StyleCop.VSPackage, Version=4.7.47.0, Culture=neutral, PublicKeyToken=f904653c63bc2738]</description>
<guid>{629EB7CC-69C2-43AC-9BC9-482B0F810C4E}</guid>
</entry>
<entry>
<record>32</record>
<time>2014/02/07 14:56:22.908</time>
<type>Error</type>
<source>VisualStudio</source>
<description>CreateInstance failed for package [StyleCop.VisualStudio.StyleCopVSPackage, StyleCop.VSPackage, Version=4.7.47.0, Culture=neutral, PublicKeyToken=f904653c63bc2738]</description>
<guid>{629EB7CC-69C2-43AC-9BC9-482B0F810C4E}</guid>
<hr>80070002</hr>
<errorinfo>Could not load file or assembly 'file:///c:\Program Files (x86)\StyleCop 4.7\StyleCop.VSPackage.dll' or one of its dependencies. The system cannot find the file specified.</errorinfo>
</entry>
<entry>
<record>33</record>
<time>2014/02/07 14:56:22.908</time>
<type>Error</type>
<source>VisualStudio</source>
<description>End package load [StyleCop.VisualStudio.StyleCopVSPackage, StyleCop.VSPackage, Version=4.7.47.0, Culture=neutral, PublicKeyToken=f904653c63bc2738]</description>
<guid>{629EB7CC-69C2-43AC-9BC9-482B0F810C4E}</guid>
<hr>80004005 - E_FAIL</hr>
<errorinfo>Could not load file or assembly 'file:///c:\Program Files (x86)\StyleCop 4.7\StyleCop.VSPackage.dll' or one of its dependencies. The system cannot find the file specified.</errorinfo>
</entry>
Closed Dec 1, 2016 at 5:05 AM by csdahlberg

comments

TomBallard wrote Feb 7, 2014 at 3:06 PM

It looks like the problem was these registry entries were left behind:

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\InstalledProducts\StyleCop
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\Packages{629EB7CC-69C2-43AC-9BC9-482B0F810C4E}

I found them by searching my registry for StyleCop. Deleting the registry keys fixed the problem.

RobertBernstein wrote Mar 19, 2014 at 7:28 PM

This happened to me today with VS 2013. I just needed to delete the registry keys above, but substituting 12.0_Config for 11.0_Config.

Thanks for the comment, @TomBallard.

Slesa wrote Sep 27, 2014 at 10:12 PM

So this error is known since Feb. and noone really cares about it?

camainc wrote Oct 20, 2014 at 5:46 PM

Stylecop is like a virus - I can't get rid of it.

csdahlberg wrote Dec 1, 2016 at 5:05 AM

This is no longer an issue starting with StyleCop 5.x (at https://github.com/StyleCop/StyleCop) since MSIs are no longer used for distribution.