Remoting throws an ambiguous match exception when you call an overloaded method that differs from another only by return value. For example,
int Foo (int a, double b); long Foo (int a, double b); The CLR seems to have no problem with this case. I've only seen the error while using Remoting so I'm not sure whether Reflection supports this case. I cannot find any statement in the metadata specs that allow/disallow this but I've read those things so many time it all begins to blue. Anyone have a pointer to the docs on this or is this a Remoting bug similar to the one I mentioned, umm, one sleep ago - maybe a couple of days... <g> -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
