Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 956953 - Last Review: August 18, 2008 - Revision: 1.0
SerializationException when calling AppDomain.SetData()
Source: Microsoft Support
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Symptom
When calling AppDomain.SetData() for a newly created domain, the following exception may be thrown:
System.Runtime.Serialization.SerializationException
    Not all delayed fixup objects could be resolved. Such objects could be cyclic IObjectReferences,
    IObjectReferences that return other IObjectReferences too many times (i.e. objects with too
    long an IObjectReference chain) or nested valuetypes
.Â
Cause
This is a bug in the listed products which can be triggered when marshaling by value a complex object, for instance a collection object containing ~100 elements, between AppDomains with the SetData call.
Resolution
This is a bug in listed versions of the .NET Framework but there are a number of ways to work around:
1) Derive your class from MarshalByRefObject so that it will be marshaled by ref instead of by value.
2) Or, set the following environment variable for the process:
    set complus_UserNewDomainRemoting=0
3) Or, use a configuration file for the application:
    <configuration>
        <runtime>
            <UseNewCrossDomainRemoting   enabled="false"/>
        </runtime>
    </configuration
4) Or, by setting a DWORD registry value HKEY_CURRENT_USER\Software\Microsoft\.NETFramework\UseNewCrossDomainRemoting to 0  (HKEY_LOCAL_MACHINE can be used as well)
MICROSOFT INTERNAL SUPPORT INFORMATION
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALSâ€) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
APPLIES TO
- Microsoft .NET Framework 2.0
- Microsoft .NET Framework 2.0 Service Pack 1 (x86)
| kbnomt kbrapidpub KB956953 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please