.Net 2.0 Exceptions won't propagate to .Net 1.1 code
In case you have a service which is compiled with .NET
2.0 and a caller which is compiled with .NET 1.1 and lets
assume that the remoting objects are interfaces that are
implemented in the service and you are using .NET remoting
for communication it works fine !
Works fine… until there is an exception in interface the
implementation code. In that case the exception cannot be
serialized back because the 2.0 exceptions use
ListDictionaryInternal class and that class is missing in
1.1. As a result the caller always receives
SerializationException instead of the real one.
Is there a way to convert the 2.0 exceptions to their 1.1
equivalent so they can be received by the caller?
Well it seems there is !
Contact PSS and mention KB #907262 and you’ll get a patch
for the interop prob.
MS plans to have this patch on the Microsoft download
center in a month so customers will be able to download it
without going through PSS.