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. Image for the cookie policy date
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

How to resolve “Syncfusion.Core assembly is not copied to the local output directory when CopyLocal is set to True”?

Platform: Miscellaneous |
Control: Install and Configuration
Tags: install

When multiple versions of Syncfusion.Core assembly is referred in a project file (.csproj), then the Syncfusion.Core assembly cannot be copied to the local output directory on building the project.

The following steps can be used to resolve this issue:

  1. Open the project file in the text editor and remove all the Syncfusion.Core assembly references except for the required Essential Studio version from the project file (.csproj).

Removing the references of unwanted syncfusion.core versions

Figure 1: Removing multiple “Syncfusion.Core” references from the project file

For example, in the above screenshot, the Syncfusion.Core assembly version 12.1400.43 is removed from the project file and only one Syncfusion.Core assembly reference is present in the project file.


  1. Make sure that the Copy Local property is set to true for all the Syncfusion referenced assemblies. Refer to the following screenshot.




Set CopyLocal to True for the Syncfusion assemblies

Figure 2: Set CopyLocal to True for the Syncfusion assemblies

  1. Now, the Syncfusion.Core assembly is copied to the local output directory.
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