Different results resharper in VS and resharper CLT

Question

My respects. Colleagues, the subject has been raised, but no answer has been found.

The results of the error check using VisualStudio 2022 plugin resharper version 2021.3.4 and resharper in CLT 2021.3.4 are completely different. The same file is used. DotSettings

There are no bugs in the IDE such as Member with the same name is already declared or Ambiguous invocation, but using the CLT there are over 2000.

The same PC is used and tried another. The result on TeamCity is the same as the CLT. Colleagues who have encountered, tell me how to solve the problem...

These items fall into the ERROR section, there is a need to exclude such errors from the output.

Thank you all

Answer 1

I had a very similar issue almost a year ago and contacted the JetBrains support. We had a very long back and forth, from which I took the following key aspects:

• There are some existing issues, for example this one.
• Make sure that no other settings layer (e.g. machine-wide config) comes into your way and overrides certain settings.
• Enable solution-wide analyses (SWA), as it comes closer to what R# CLT does.
• The whole picture becomes even more fuzzy when using Rider. For example, I had to enable File | Settings | Editor | Inspection Settings | " Enable computationally expensive inspections"
• There are different results shown, depending on the used tool window.
  • Rider
    • SWA
    • Code ? Inspect Code
  • VS
    • SWA
    • ReSharper ? Inspect ? Code Issues in Solution

So my key take-away was: it is super-hard to reach a 100% sync of VS and R# CLT, which gets even more complex when Rider comes into play. The almost inexhaustible number of options to configure R# makes it impossible to answer your general question.
What I can recommend: try to reduce the problem to a very small solution and get in contact to JetBrains.

Answer 2

I finally found a solution to my problem. The code used the Blazor component and files with the razor extension produced a large number of bugs that VS did not see. This was corrected in the new version of R# 2022.1.0