ReSharper Command Line Tools

Hi,

Our developemnt team is running ReSharper 7.1.3 and our CI server is running InspectCode 8.2.1 (Although we are able to use version 8.2.0). I have found that the XML report generated within Visual Studio differs from the one created by InspectCode (please see attached). I'm assuming this is to do with the version / build of InspectCode versus ReSharper Code Inspection (I might be wrong).

Is our only option to upgrade all our users to the latest version of ReSharper to ensure parity with the version of InspectCode on the build server, or is there another option?

Thanks,
Gordon

6 comments
Comment actions Permalink

For some reason, I can't see your attachments, so I will take a shot in the dark here.

We are also using InspectCode in our build process, and the main difference is that inspectcode does solution wide analysis by default, while resharper's code inspection in Visual Studio does not.

Perhaps you could try using the '/no-swea' command line argument on the tool and then comparing the results (or alternativelly, enabling solution wide analysis in Visual Studio).

Out of curiosity, what build tool are you using? We use TFS 2013 here.

0
Comment actions Permalink

Hi Juliano,

Apologies for the late reply, I have been away.

I disabled solution wide analysis for inspect code, and the difference was negligable. I have a script that parsers the XML generate from inspect code and reports on any issue types which are errors. As can be seen from the 3 attached files, the difference seems to be related to the underlying version of inspsect code running (whether within VS or command line). I cant seem to find inspect code version 7.1.3 to test my theory but needless to say that if our developers run code analysis within visual studio, the findings are different to what is generated on the CI server (bamboo).

Thanks,
Gordon



Attachment(s):
inspectcode.8.2.1.txt.zip
visualstudio.7.1.3.txt.zip
visualstudio.8.2.1.txt.zip
0
Comment actions Permalink

There isn't a 7.1.3 version of inspectcode.exe, it was only introduced with ReSharper 8. You shouldn't see any differences between ReSharper 8.2.1 and InspectCode 8.2.1, however, you should expect to see differences between ReSharper 7.1.3 and ReSharper 8.2.1, as it's a major version change in the product.

0
Comment actions Permalink

Ok thanks!

So i guess if we want to use inspect code in tandem with visual studio resharper we will need to upgrade all our licenses from version 7.1.3 to 8.2.1, is this correct?

Also, i noted that the old version was looking for the folowing issue whihc doesnt exist in the new version and therefore has a different error count (just as a fyi);

<IssueType Id="PublicMembersMustHaveComments" Category="Potential Code Quality Issues" Description="Public members should have XML documentation" Severity="ERROR"/>

Cheers,

0
Comment actions Permalink

If you want to be sure that you've got the same set of analyses and warnings, then yes, it's best to have the same version on the build server as on the desktop.

As for that particular warning, I think it's changed to PublicOrProtectedMemberNotDocumented in 8.x, and it lives under the CompilerWarnings group. It will only show up as an error if your project has enabled warnings as errors.

0
Comment actions Permalink

Hi Matt,

Our company will be upgrading to the latest version next month so fortunately the version issue should be resolved.

Thanks you kindly for the help!

0

Please sign in to leave a comment.