TypeLoadException (method not implemented) when starting stylecop

[stylecop]

TypeLoadException (method not implemented) when starting stylecop

[ThielHater]

I came from #123 and have the same problem as @GeneralSan. The only solution so far is to delete all "yworks*.dll" files from "%localappdata%\JetBrains\Installations\ReSharperPlatformVs15_8617f09a". Of course this isn't a proper solution as yWorks is a diagram component which is part of ReSharper.

This error happens only when StyleCop.ReSharper is installed, but the issue tracker is disabled for that repo.

[citizenmatt]

Is this running the StyleCop command that's implemented by the Visual Studio plugin?

I wonder if this is an issue to do with the strong naming of the StyleCop.dll assemblies - it means both the ReSharper plugin and the VS plugin can ship different versions without problems, but if they ship the same version, either assembly can be used. But, if the VS code uses the ReSharper assembly, I bet it's trying to load the rules by looking at the folder containing the StyleCop.dll file, which is the ReSharper bin folder, and it's therefore having problems with the obfuscated yWorks assembly. Hmm.

Can you let me know the version numbers of ReSharper, the ReSharper StyleCop plugin and the VS StyleCop plugin, please?

[GeneralSan]

It is the Visual StyleCop extension command.

I use the official version of Resharper Ultimate. (no betas or anything)
Without looking up specific versions, I have installed the latest resharper
this morning (update from today/yesterday, so the absolutely latest
version).
There are no updates for the resharper stylecop extension, so this should
also be the latest version.
There are no updates for Visual StyleCop, so also the latest version.

To check the actual version numbers:
VS 2015 Update 2
Visual StyleCop 4.7.59.0
Resharper Utimate 2016.1.1
StyleCop by JetBrains 2016.1.0

---

Met vriendelijke groeten,
Dirk Maegh

On Fri, May 6, 2016 at 11:45 AM, Matt Ellis [email protected]
wrote:

Is this running the StyleCop command that's implemented by the Visual
Studio plugin?

I wonder if this is an issue to do with the strong naming of the
StyleCop.dll assemblies - it means both the ReSharper plugin and the VS
plugin can ship different versions without problems, but if they ship the
same version, either assembly can be used. But, if the VS code uses the
ReSharper assembly, I bet it's trying to load the rules by looking at the
folder containing the StyleCop.dll file, which is the ReSharper bin folder,
and it's therefore having problems with the obfuscated yWorks assembly. Hmm.

Can you let me know the version numbers of ReSharper, the ReSharper
StyleCop plugin and the VS StyleCop plugin, please?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#50 (comment)

[citizenmatt]

Thanks. I do think it's the situation I described. That's going to need a little thought on how to fix, unfortunately.

[bjornsallarp]

Everyone in my team has the exact same problem. It would be really awesome if this could be solved or if Resharper By Jetbrains could add a context-menu item to scan all files that mimic the original plugin.

[KJee85]

Any updates on this issue? I'm still seeing it with

StyleCop.MSBuild Nuget: 4.7.54.0
ReSharper: 2016.2.2
StyleCop by JetBrains: 2016.2.1

I almost got around it by adding StyleCop.dll from nuget package to GAC but this actually caused StyleCop in general not to actually scan on build even with addin uninstalled.

[AjayJS]

Hi,

I am also facing the same issue.

Regards,
Ajay.K

[SveinungFjaer]

Any news on this issue?

[matkoch]

This should be adressed by #167. Let's wait for @csdahlberg review.

[ThielHater]

In the meantime I found out that the error happens in StyleCopCore.LoadAddins() while processing "yWorks.yFilesWPF.Viewer.dll". That function is called by StyleCopCore.Initialize(), having the parameter "loadFromDefaultPath" set to "true". I don't know if the pull request of @matkoch fixes this error, because I have problems compiling the StyleCop.VisualStudio project, but I guess it does.

[daniel-cohen]

@ThielHater Thanks ! renaming "yWorks.yFilesWPF.Viewer.dll" seems to be a work around.