|106819||Jan 28,2013 04:54 AM||Jan 31,2013 06:46 AM||Windows Forms||1|
But we didn't face this issue with this same project when we compiled it using Syncfusion Essential Studio 126.96.36.199 assemblies.We came to know that the above mentioned TYPES belong to the namespace SYNCFUSION.WINDOWS.FORMS.DIAGRAM which is a part of SYNCFUSION.DIAGRAM.BASE.dll.
We used the reflector to open SYNCFUSION.DIAGRAM.BASE.dll & then opened the SYNCFUSION.WINDOWS.FORMS.DIAGRAM namespace & there we found that the above mentioned types are not present , which was there in 188.8.131.52 version of essential studio.(we opened the 184.108.40.206 assemblies in reflector to compare & cross-check)
So , plz let us know in which new version release these types were removed or replaced , bcoz we went through the release notes of the latest version (i.e10.4.0.71) & also the release notes of the previous versions , but couldn't find any information regarding the above types.
So,kindly help us by giving some useful suggestions on how to solve this issue so that we could in future switch over to the latest version of the syncfusion essential studio at the earliest.
Note:At present we just downloaded the evaluation vesrion of 10.4.0.71 just to check how projects work with new essential studio assemblies.
Santhosh A V
Thanks for using Syncfusion products.
Since we have made several API changes to make diagram more stable and maintainable, and the new version of diagram provides more usability and supportability, we suggest you to refer the following migration documents and make the appropriate changes where it is needed.
The migration document can be downloaded from the below link.
Please follow the procedure in the above migration documents and let me know if it helps.
To know more about the usage of Diagram classes and properties, please visit our below online documentation link:
Please let us know if you have any queries.
Amsath Ali. M
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.