Attention: We are retiring the ASP.NET Community Blogs. Learn more >

I think this was a compliment

Over the course of 2+ years, we have had to call MSDN Support approx 10 times with bugs in the framework we simply cannot resolve.  The good and bad news, we have never been charged as all of the bugs were true framework bugs.

Today, after about 3 weeks working on our latest incident, the MS rep called me, gave me a work around and said "I always enjoy working with you folks as your cases have a twist to them".  This time they found a design limitation in calls to assembly.LoadFrom that we hit up against.  

I'll take this as a compliment  ;-)

 

    

2 Comments

  • >his time they found a design limitation in calls to assembly.LoadFrom that we hit up against.



    What was it?

  • From MSDN support:



    "Here is a summary of the issue for your records:



    Action:

    You had added custom error handling to the Microsoft ExceptionManager PAG assembly and then attempt to use LoadFrom to load the Assembly.



    Result:

    The following error message was displayed:



    Exception Type: System.InvalidCastException

    Message: Specified cast is not valid.



    This error does not occur when the assembly is loaded locally.



    Cause:

    This error is generated because of a design fault in the .NET Framework in that we are unable to resolve the information from the configuration file.



    Resolution:

    We were able to resolve the issue by loading the assembly in the Load context within a new AppDomain, then using .NET Remoting to marshal a type which derives from MarshalByRefObject into the new AppDomain, which then loads the target assembly for you. We provided a working model and the associated code is attached to this case should you need a new copy in the future and it is expected to be included in a Knowledgebase article in the near future."

Comments have been disabled for this content.