Broad Solution Analysis Broken in Resharper 4.5?

Question

I am having problems with a wide analysis of solutions since I upgraded to version 4.5.

I constantly get false negatives, and I get report errors with my code that does not exist.

I believe that the only way to get rid of errors is to open each of the errors reported in the files, find the offensive types / classes, open these files, and then close everything again, which seems to make you re-examine everything.

I believe there is a defect already @jira, but I am looking for useful tips on how to quickly get resharper to re-analyze files by mistake ...

Answer 1

When this happens to me, I use shift + alt + Page-Down to scroll to the next error in the solution. A simple reading of the errors will force Resharper to re-analyze the files. Not a good solution, but it works.

Edit: If you go to the menu ReSharper → Windows → “Errors in the solution”, you will get a window called “Errors in the solution”. There you have a button on the right called "Reanalyze Files With Errors". You can even put a shortcut.

Answer 2

Delete your re-access cache files regularly, especially if you upgraded from a previous version. Most likely you have a _Resharper file. * Somewhere in the folder with your solution. All this folder structure can be removed, and when Resharper doesn’t work for me, I do it.

Answer 3

Depending on how big your solution is, this can be a huge pain, but sometimes I have the same problem, and if I create a project showing errors, it goes away.

For example, only yesterday he could not find the Excel library for one of our small projects, and it was completely red, although nothing had changed, all the DLLs were found and mentioned, and nothing had been done explicitly. I just rebuilt this individual project, it compiled without errors, and the red bars immediately disappeared.

Answer 4

It looks like the problem is in the resharper. It is usually best to report this directly and then wait until they find out about this matter.

In addition, this is more a bug report than a programming issue.

Answer 5

The same thing here, but then again I get false positives (or negatives) for ages. Two points of failure for me are WPF (especially XAML) and the use of Unicode in code files (i.e., Programming using non-Latin letters).

I would suggest just turning it off, especially considering the execution price you pay for it.