Ask a questionAsk a question
 

AnswerTypeLoadExceptionHolder

  • Wednesday, September 13, 2006 2:41 PMcbmikee Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I'm trying to deserialize an object (serialized in .NET 1.1) in .NET 2.0 and one of the child objects is causing a TypeLoadExceptionHolder to be substituted for it in the SerializationInfo during the deserialization process.  This same serialized object will deserialize fine using the same code base built under .NET 1.1.  I cannot find any information on what a TypeLoadExceptionHolder object means or why it is being put in the serialization info slot for the child object.

    Any help would be appreciated.

    Thanks!

Answers

  • Wednesday, September 13, 2006 3:56 PMcbmikee Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Turned out to be a case sensitivity problem.  The type serialized had a character with a different case than the type that actually exists.  It appears 1.1 doesn't care about this, but 2.0 does.  Can 2.0 be set to 1.1's more lax case sensitivity?

     

    Thanks!

All Replies

  • Wednesday, September 13, 2006 3:56 PMcbmikee Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Turned out to be a case sensitivity problem.  The type serialized had a character with a different case than the type that actually exists.  It appears 1.1 doesn't care about this, but 2.0 does.  Can 2.0 be set to 1.1's more lax case sensitivity?

     

    Thanks!

  • Thursday, September 14, 2006 7:18 AMLucian Bargaoanu Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    This assert is correct both in 1.1 and 2.0

    Debug.Assert(null == Type.GetType("System.int32"));