I think there is a bug in the Serialization/Deserialization code for Exceptions and its derivatives. Consider the following scenario: Two AppDomains A and B, both with a different codebase. (Remoting scenario would show the same behaviour, I guess) An exception occurs in a component inside B. The component inside B is unknown in A. The exception is send to A. A receives the exception, and can succesfully use any public property (except TargetSite). If I try to serialize this exception again in A, I get a FileNotFoundException because it can not find the assembly that threw the exception. This is behaviour I do not expect, as I was able to succesfully DEserialize. IOW: It already has all the information to serialize itself again.
Is this a bug, or is this designed behaviour? Robert NB The TargetSite property on this exception in A gives a FileNotFoundException, because it can not find the assembly that threw the exception. This, to me, is expected behaviour =================================== This list is hosted by DevelopMentorŪ http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London and Boston http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
