We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Removing version information when serializing a Diagram that contains custom Symbol with SaveBinary

Thread ID:

Created:

Updated:

Platform:

Replies:

126163 Sep 28,2016 04:31 AM Sep 29,2016 07:35 AM Windows Forms 1
loading
Tags: Diagram
Marco Casella
Asked On September 28, 2016 04:31 AM

I have a diagram with some custom symbol 

    [Serializable()] public class CustomNode : Group { protected CustomNode(SerializationInfo info, StreamingContext context) : base(info, context) { this.m_nodeInformation = info.GetString("strDescription"); } protected override void GetObjectData(SerializationInfo info, StreamingContext context) { base.GetObjectData(info, context); info.AddValue("strDescription", this.NodeInformation); } }
Then i serialize the entire diagram with:

 diagram1.SaveBinary(this.FileName);

and later load with:

diagram1.LoadBinary(this.FileName);



The probleim is that this serialization contains the version of the assembly of my class, and when it changes old node won't be deserialized.

There is a method to customize this?


best regards
Marco


Naganathan Ganesh Babu [Syncfusion]
Replied On September 29, 2016 07:35 AM

Hi Macro, 
Thanks for contacting Syncfusion support. 
On further analysis, we found that the problem is due to the AssemblyResolver error. Please refer to the below online KB documentation link for your references. 
https://www.syncfusion.com/kb/5703/Adding-OldToNewDeserializationBinder-for-loading-old-versioned-edp-file-in-new-version 
Regards, 
Naganathan K G  


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;