Question

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.

Answer 1

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.