)
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. (Last updated on: June 24, 2019).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

How to avoid assembly conflicts?

Platform: Miscellaneous |
Control: Install and Configuration |
Published Date: May 18, 2016 |
Last Revised Date: December 5, 2019

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 Essential Studio 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.

 

 

ADD COMMENT
You must log in to leave a comment

Please sign in to access our KB

This page will automatically be redirected to the sign-in page in 10 seconds.

Up arrow icon

Warning Icon 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.Close Icon

Live Chat Icon For mobile
Live Chat Icon