ReSharper says "Ambiguous invocation" but everything builds and works

I've got some strongly typed DataSets I'm using in a large ASP.NET website. Every time I reference any method from these DataSets, ReSharper flags it as ambiguous with a red underline. All the code builds, and works perfectly, but ReSharper is showing me hundreds of these "Ambiguous invocation" and "Ambiguous reference" errors.

I've attached a couple screenshots of what I'm talking about. Please advise. This is incredibly annoying, as I can't differentiate "real" errors from ReSharper errors.



Attachment(s):
Ambiguous_Invocation_001.png
Ambiguous_Invocation_002.png
14 comments
Comment actions Permalink

"Matt Blodgett" <mblodgett@rpionline.com> wrote in message
news:25776964.1172773535238.JavaMail.itn@is.intellij.net...

I've got some strongly typed DataSets I'm using in a large ASP.NET
website. Every time I reference any method from these DataSets, ReSharper
flags it as ambiguous with a red underline. All the code builds, and
works perfectly, but ReSharper is showing me hundreds of these "Ambiguous
invocation" and "Ambiguous reference" errors.

>

I've attached a couple screenshots of what I'm talking about. Please
advise. This is incredibly annoying, as I can't differentiate "real"
errors from ReSharper errors.


Which version of ReSharper are you using? They've already fixed some of
these errors.

John


0
Comment actions Permalink

I'm using ReSharper 2.5 build #326 (2.5.326.1)

0
Comment actions Permalink

Matt,

It's a very old one. I've fixed a number of similar issues in builds
50-something. I would recommend the most recent nightly build, which you can
find at
http://www.jetbrains.net/confluence/display/ReSharper/Nightly+Builds

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I just installed build #360, and it seems to have fixed the problem. I'll be back if it reverts to its old tricks in the next few days.

0
Comment actions Permalink

The problem has appeared again in a slightly different form.

Now it's only affecting my code that references methods and properties of a web service.

0
Comment actions Permalink

Matt,
Could you describe it more precisely?

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I would give you an example of that, but the problem comes and goes. It seems almost totally random. It might appear like 1 out of every 3 times I open Visual Studio.

But...I do have a screenshot for you of another "fake error" situation caused by ReSharper. This time ReSharper is telling me "Cannot resolve symbol 'HyperLinkField'" in code that builds and works perfectly.

I really never know when ReSharper is going to show me fake errors. It happens in different code files at different times. It seems totally random.

I've attached another screenshot of ReSharper telling me "Cannot resolve symbol 'QueryStringParameter'" in code that builds and works perfectly.



Attachment(s):
HyperLinkField.png
QueryStringParameter.png
0
Comment actions Permalink

Matt,
Could you describe it more precisely?


I'm seeing the same error in build 361 on all members of strongly typed-datasets, as shown in the screenshot.

Attachment not added (general error): "screen1.jpg"

0
Comment actions Permalink

I also see issue on my typed datasets.

My situation appears related to namespaces.

I get error when including namespace with using directive at top of class file.

If I qualify the name(s) to the DataSet/DataTable, I eliminate error - but I have to eliminate them all else get casting error instead.

Very annoying.
-Rob

0
Comment actions Permalink

Hmm, dead strange? Could you create a sample solution for us?

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hmm, dead strange? Could you create a sample solution for us?


Who? Me?


0
Comment actions Permalink

Why not? Was not that you who commented 'I'm seeing the same error in build
361 on all members of strongly typed-datasets, as shown in the screenshot' a
couple of messages earlier?

In fact, I would appreciate anyone's solution, with which the problem is
reproducible.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I would send a sample, but last yesterdays build seems to have fixed the issue.

Crossing my fingers won't see it again.

0
Comment actions Permalink

Why not? Was not that you who commented 'I'm seeing the same error in
build 361 on all members of strongly typed-datasets, as shown in the
screenshot' a couple of messages earlier?


I found I could not reproduce the error in a smaller sample, but the error
persisted in my original solution. What could be different, I wondered? Well,
the _Resharper* reflection cache and index directory created by the pre-361
builds were still in my temp directory. When I renamed this directory, the
Resharper error messages went away. When I replaced the directory, the messages
returned.

I suggest users with erroneous error messages rename the project's Resharper
cache from older builds and see whether you get the expected results from
Reshaper.


0

Please sign in to leave a comment.