Inspections (.NET) differences and exceptions after upgrade from TC 7.1.3 to 8.0.5

Hello,

for several .NET solutions we are using the Inspections (.NET) runner to report ReSharper errors and warnings. After upgrading to TC 8.0.5, in small solutions (3-5 C# projects) the number of warnings increased by a few hundred issues. There are also some new issues like 'Use ////-comment' which are reported at places where we use '// Resharper disable ...' comments. We are using a custom settings layer which is mounted and solution-wide analysis is disabled (according to the build log).
Bigger solutions (~50 C# projects) end up in System.OutOfMemoryException.
Is there a way to get the inspection tool back to the version used in TC 7.1.5 to be running with TC 8.0.5?
How is R# versioning handled?
Can the R# version of the TC inspections runner be changed so that it matches the version the developers have installed?

Thanks,
Helios

8 comments
Comment actions Permalink

Any update on this issue?
The Inspections (.NET) report is part of our monthly development report and we would like to have a solution for this issue.

Thanks,
Helios

0
Comment actions Permalink

After reproducing this issue with an empty C# project where the inspections report shows no errors/warnings using TC 7.1.3 (and TC 7.1.5) it shows me a wrong report in TC 8.0.5, e.g. 'redundant using directive' which is wrong as it doesn't compile without the using directive.
Also, in TC 8.0.5 the wrong number of warnings and errors is different on agents with and without VisualStudio installation, which is not the case using TC 7.1.x.
For now, I've replaced the Inspections plugin by the one from TC 7.1.3 and our reports work again as expected. (also the OOM exceptions are solved)

0
Comment actions Permalink

Hello,
Could you please install fresh version of the plugin and let me know if it fixws your problems or not?

0
Comment actions Permalink

Hi,

also with this version I'm having the issues described above. Tried on my testing environment.
Looking at the build log I see the following entries when using this new version which differs from the successful build:

[Step 1/1] InspectCode 8.1.37.8
[Step 1/1] The OutputPath property is not set for project 'TeamCityTest.csproj'.  Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.  Configuration='Debug'  Platform='MCD'.  You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Configuration or Platform that doesn't exist for this project. in file 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets' at (609:5)

The second mesage is in red and also exists in the build log using the TC 8.0.5 version. The output path property is set for Debug and Release in the csproj file.

0
Comment actions Permalink

Please check that you can succesfully build this project via MSBuild on problemmatic build agent.

0
Comment actions Permalink

Added a compile configuration using an msbuild runner and it compiles successfully.

Still the same errors.
The C# Compiler Errors show that it has an issue with finding system assemblies.
Cannot resolve symbol 'Application'
Cannot resolve symbol 'Windows'
Cannot resolve symbol 'Form'

and in the redundant using directive it says that this using directive is not required. (System.Windows.Forms)
Not only .NET assemblies but also additional assemblies like NUnit which are not installed in the GAC.
Also tried to select both .NET 4 and 4.5 or none for the target framework of the inspections runner.

0
Comment actions Permalink

Could you please create issue in our tracker? Also please attach problemmatic .csproj file and build logs with debug output turned on. I'll take a look on it.

0

Please sign in to leave a comment.