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.

How to avoid assembly conflicts?

Visual Studio throw errors when multiple version of Syncfusion assemblies or different framework version assemblies are referring in project. As Syncfusion supports Multiple Versions, you can have more than one version of Syncfusion setup installed in a machine. But Syncfusion doesn’t allows multiple version Syncfusion assemblies or different framework version assemblies in a same project.

Assembly version mismatches while manually upgrading your project references to the latest Syncfusion version by manually removing and adding the reference. While upgrading manually, you might miss some of the reference. So, assembly conflicts in this situation.

In order to avoid such conflicts, you can use the Syncfusion Project Migration utility for upgrading your project references to the latest Syncfusion version. Please refer Project Migration to know more about Syncfusion Project Migration utility.

 

 

Article ID: Published Date: Last Revised Date: Platform: Control:
6891 05/18/2016 05/18/2016 Miscellaneous Install and Configuration
Tags:
Did you find this information helpful?
Add Comment
You must log in to leave a comment

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.