Unexpected behaviour when calling overriden method

Since not too long ago, I joined the MSDN Forums. The MSDN Forums is a big community where lots of knowledge is passed around. I recommend joining.

Yesterday I ran into an interesting post. It’s about an overriding method that exactly seems to match the call, but doesn’t get called. In stead, the base method is called… Apparently this is because of override-resolution starting at the base working its way up, and a method declaration that matches more than you would think it does.

You can find the thread here.

• dotnet