Interface same name of methods problem

[MaLiN2223]

I believe I encountered a bug. I'm working on .NET Core 2.0.

Those are my interfaces:

  public interface A<T>
  {
  }
  public interface B<T>
  {
  }
  public interface X
  {
    Task<K> Foo<K>(B<K> bar);
    Task<K> Foo<K>(A<K> bar);
  }

When I'm trying to substitute X this is an exception that occurs:
System.TypeLoadException : Method 'Foo' in type 'Castle.Proxies.XProxy' from assembly 'DynamicProxyGenAssembly2, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.

I think it has something to do with the fact that those methods have the same name because when I change second method's name to Foo2 everything works.
Is there anything I can do to make this example work without changing an interface?

[alexandrnikitin]

Good catch! It's related to Castle.Core issue castleproject/Core#309
I'll update the version constraint.
Thank you!

[zvirja]

@alexandrnikitin If I got it clear, issue has been already fixed in v4.2.1. Therefore, as a temporary fix, @MaLiN2223 could update the Castle.Core dependency to the most recent one.

Should NSubstitute also change the minimum Castle.Core version in v4?

[alexandrnikitin]

Yes, correct. Updating Castle.Core to 4.2.1 should fix the issue.