VS 2012 v11.0.61030.0
At my company we have a large solution (circa 80 projects) which are a mixture of C# and F#.
We have started upgrading to R# 8.2 and are seeing some problems from time to time when building the solution. This does not happen at all for developers that are still using R# at earlier versions, upto and including 8.1.
This is what happens:
The developer is making changes to a C# project, and building, debugging and running unit tests. Everything is ok.
The developer makes an inconsequential change to a C# source file and attempts to run the unit tests again.
The environment attempts to re-build the solution and it fails with a couple of errors. The error message concerns a failure to find an F# assembly in a particular location. Note that the particular location is COMPLETELY WRONG, being way too close to the root of the relevant drive (e.g. the F# assembly lives in C:\a\b\c\d\e and the environment is looking for it in C:\a\b)
Trying to build again produces a greater number of errors. As each attempt is made, the number of errors spirals (I've seen over 1000 eventually).
Here's the strange thing, and the reason I'm raising this issue on this forum:
The only way found to resolve the issue so far is to disable and then re-enable R#. Usually after doing this the solution builds fine, until it randomly fails again sometime later. I say "usually" because on one occasion I have also had to stop and restart VS after disabling and re-enabling R#.
I have also noticed that when I come to commit changes sometime later that sometimes there are temporary files (2x .TMP files) that have been produced by R# that suggest that it has managed to corrupt its user settings file for the solution at some point.
Might this issue be connected with the issue "ReSharper 188.8.131.520 Breaks Solutions" elsewhere on this forum?
I haven't yet managed to come up with a consistent way to reproduce the issue yet, so cannot post them here.