Return to Question

Here if I try to do a typeof(I3).GetProperties() I don't get the Current property (and this is something known, see for example GetProperties() to return all properties for an interface inheritance hierarchy), but I can't simply flatten the interfaces, because then I wouldn't know who is hiding who.

Here if I try to do a typeof(I3).GetProperties() I don't get the Current property (and this is something known, see for example GetProperties() to return all properties for an interface inheritance hierarchy), but I can't simply flatten the interfaces, because then I wouldn't know who is hiding who.

Note:

after thinking for another half an hour, the problem for the classes is easily solvable:

public static MethodInfo GetMethod(Type type, string name, Type[] types)
{
    while (type != null)
    {
        var method = type.GetMethod(name, BindingFlags.Public | BindingFlags.Instance | BindingFlags.DeclaredOnly, null, types, null);

        if (method != null)
        {
            return method;
        }

        type = type.BaseType;
    }

    return null;
}

This works because C# (and .NET) uses single inheritance. I simply walk upward (technically this is wrong wrong wrong if I'm importing a VB.NET assembly, because VB.NET uses hide-by-name instead of hide-by-signature, so a method with the same name but different parameters could shadow the member you are looking for that is present in a base class). And for interfaces?

After some thought it's clear that there is something similar in the Microsoft.VisualBasic assembly. VB.NET supports late binding. It's in Microsoft.VisualBasic.CompilerServices.NewLateBinding, but it doesn't expose the late bounded methods.

Clearly if I try typeof(C3).GetProperty("Current") I get an exception.

This works because C# (and .NET) uses single inheritance. I simply walk upward. And for interfaces?

Clearly if I try typeof(C3).GetProperty("Current") I get an AmbiguousMatchException exception.

This works because C# (and .NET) uses single inheritance. I simply walk upward (technically this is wrong wrong wrong if I'm importing a VB.NET assembly, because VB.NET uses hide-by-name instead of hide-by-signature, so a method with the same name but different parameters could shadow the member you are looking for that is present in a base class). And for interfaces?