visual studio 2012 - How to use the StyleCop Plugin with the Resharper command line or "InspectCode" tool -

We use Resharper with the StyleCop plugin. It works great inside Visual Studio without any problems

Now I want to get statistics about our projects. I am creating all our solutions from the command line and so far the compiler Warnings) Stable code analysis (formerly FxCop) and unit testing (results and coverage) have been able to get output.

JetBrains provides a commandline tool that performs code analysis for free ().

I am using it and it works as expected

The command line version can not recognize my StyleCop plugin and its rules are. It's clear, this is a separate folder, so I have to put my plugins folder at

C: \ Program Files (x86) \ JetBrains \ ReSharper \ v8.2 \ Bin \ Plugins \ StyleCop 4.7 Copied

of the command line tool. Bin \ plugins \ styleCop 4.7 is more than my installer and it works ... The command line tool recognizes the plugin and loads it. However, the plugin can not then get the style coop assembly. They are installed by default

C: \ Program Files (x86) \ Stylescope 4.7

To detect yourself in Visual Studio They can detect them in any way.

I tried copying the stylecong assembly to the same folder that is in the Command Line X. Nothing changed.

I tried copying StyleCop assemblies next to the StyleCop plugin assembly, that worked in a way, the stylecope plugin found it styled coop assemblies, but the command line tool complained because of that plugin As an attempt was made to load every single assembly in that folder.

How do I use the command line tool for the StyleCap plugin?

If there is a better option, then I have a full license, I am happy about any indication that this free command line tool or general resharper until I use Visual The Studio GUI can start with a batch file without opening it until the full version.

current state

Rushdorp has recognized that it is a there is a problem. The issue is #

it is not fixed as 2017.1.1 .

Solution

When a nozzle package (extension .nupkg ) is found in the folder of the device, it gets automatically expanded in some temporary location is. After this the assemblies are used with the equipment.

Then any * .nupkg of the plugin in the tool folder should work.