I doubt anyone else will run into this bug however I'm posting it for the archives.
The CLR determines uniqueness of a member of a class using the name/signature tuple. That is, the CLR is perfectly happy encountering an 'int a' and a 'double a' in the same scope. Unfortunately, I found out last night, the deserialization part of remoting isn't. It relies on uniqueness of names only. This is a known bug and will be fixed in some future version. -- 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.
