CODEWITHSUNDEEP
c#build.net-3.5
Gluip
Gluip

Reputation: 2987

compiler build error : The call is ambiguous between the following methods or properties

I am experiencing a strange compiler error with extension methods. I have an assembly which has an extension method like 

public static class MyClass
{
    public static Bar GetBar(this Foo foo)
    {
        return new Bar();
    }
}

And elsewhere in the same assembly i do something like this

Foo foo = new Foo();
var bar = foo.GetBar();

When i clean and compile everything is OK. BUT once i make a small change (like an extra whitespace) in the assembly and build again I get an error like this:

Error 973 The call is ambiguous between the following methods or properties: 'MyNameSpace.MyClass.GetBar(Foo)' and 'MyNameSpace.MyClass.GetBar(Foo)'

Only after i clean the project I can build again. Is this a problem in the compiler using an old version of the assembly? Only work around I see now is to replace my extension methods with normal static methods.

Upvotes: 15

Views: 7950

Answers (4)

StrictLine
StrictLine

Reputation: 85

I've had this behavior upon compiling with MSBuild v14:

  • building in VS 2015 worked just fine
  • building on the same machine by MSBuild worked also
  • building on a server machine with only MSBuild preinstalled failed

Installing the .NET Developer Pack (in my case Developer Pack for 4.5.2) solved the issue, even if the error message was misleading.

Upvotes: 0

Carra
Carra

Reputation: 17964

Took me a while to figure this one out but Gluips comment is the right one, I'll add it here for easy reference:

That's it! Somehow the project was directly referencing itself. Removing the reference probably fixes the problem. Thanks!

This fixed it for me.

Upvotes: 27

Justin
Justin

Reputation: 86729

Ok having done a bit of playing round I can reproduce a similar situation to this by adding a file reference to the output file - the first time round it builds successflly (as the reference is not used - you simply get a "reference not resolved" warning), however from this point on I see the "The call is ambiguous" error appear in the code editor.

For me however this doesn't prevent me from building the solution (I'm testing this using Visual Studio 2010), however the error does appear - maybe under slighly different circumstances, such as a different Visual Studio version, this would stop the project from compiling.

You could also engineer this same situation with post-build steps that copy the output assembly.

Upvotes: 4

Sergey Metlov
Sergey Metlov

Reputation: 26291

I can't explain such behavior, but you should implement such method as a static directly in Foo class.

Upvotes: 0

Related Questions