Much better than the previous build, but there's still a couple of projects
in my over-all solution where I'm getting bogus "Ambiguous Reference"
errors, and a bogus "Duplicate Definition" error on some classes.
If I position the cursor on the "Ambiguous Reference" error and Goto
Definition, it'll show two identical defitions for me to choose from (no
difference at all). If I click one, I'm taken to the object browser, and if
I click the other, I'm taken to the actual class. It's this class that is
flagged as "Duplicate Definition". If I right-click Goto Definition, it
takes me to right where I am, no indication that there are multiple class
definitions. I don't know where it's getting this from.
I do believe this must be due to the DLL refereces though. And I think I
might know why. We (for reasons unknown to me, but it's not changing) have
two bin directories where DLLs are copied to... one for the application, and
one for tests to run from. Don't ask why, I don't know. But I think maybe
it's somehow seeing a reference to ABC.DLL in one of those directories as
somehow different than a reference to the same ABC.DLL in the other
directory. I say this because I'm only seeing the problem in my test
projects, not any of the other ones.
What that doesn't explain, though, is why the class "Foo" in my TestSetup
proejct is flagged as a duplicate. It's only declared in this one file,
period... I have no idea what Resharper is looking at to think there is
another copy of this class somewhere.
Obviously there are no partial classes involved, no duplicate class
definitions, and it builds and runs just fine. ReSharper is just getting
confused somehow, somewhere.
Since all my non-Test projects and classes are fine, at least I don't have
to roll back to a previous version of Resharper, but this still is a serious
issue, and this wasn't a problem in previous builds so it's a regression.
If there's something specific I can look at or give you information about,
I'll be more than glad to try and help out.