ReSharper 7.1 "Cannot Resolve Symbols"

Hello,

I remember reporting this issue back then when I had R# 6.0 and you told me that it's a bug in the editor, only that when I disabled R# everything got back to normal! the same thing happens in the latest release,yet again, disabling R# solves the problem.

I'm not sure whether it's the same bug but it's pretty annoying...

8 comments
Comment actions Permalink

Hello,

We apologize for the inconvenience.
Could you please create and send me a small sample solution, which will demonstarte the issue?

Thanks!

0
Comment actions Permalink

Well, I can't send you the project I'm working on because it's proprietary and making a new project on my machine wouldn't make any difference so you can really use your test projects there and reproduce it.

I'll try to reproduce it with a sample project and write the steps once I'll have the time.

0
Comment actions Permalink

Hello Eyal,

This kind of an issue does require us to have a sample. 'Cannot Resolve Symbol' issue does not affect normally (on our test projects as well).
Still, there are some known cases, where ReSharper will mark symbols with 'Cannot resolve' message - for example, when symbols (e.g. methods) are declared in an external assembly, which is referenced to the main solution you are working with dynamically, like the assemblies which are built on the 'Solution Build' action.

If it's not your case, it might be a bug in ReSharper; however we still need a repro case for this.
If  you can't provide us a sample, we will appreciate any information about this - like, .net framework version, types of unresolved symbols, how are they referenced, etc. - anything can help us in this case.

Thank you.

0
Comment actions Permalink

I'll provide more information the moment it will happen, so it may take some time.

Thank you for the support.

0
Comment actions Permalink

You are welcome!
Thank you in advance, Eyal!

0
Comment actions Permalink

Just wanted to say that it rarely happens now.

0
Comment actions Permalink

I am also receiving this issue with ReSharper 7.1.2 when using Fluent Assertions (http://fluentassertions.codeplex.com/).

Example:
subscriptions.Should().BeEmpty();

The BeEmpty method cannot be resolved by ReSharper.

Example:
subscriptions.Should().Contain(Subscriptions[1]);

The Contain method cannot be resolved by ReSharper.

Any help will be appreciated.

0
Comment actions Permalink

Hello Jeremy,

I've logged this issue in YouTrack here for our QA Team to check it: http://youtrack.jetbrains.com/issue/RSRP-350567
Thank you for the report!

0

Please sign in to leave a comment.