1. Home
  2. Forum
  3. General Discussion
  4. Assembly mismatch error

Assembly mismatch error

while am debugging one windows application done using VS2003 am getting the error..


The located assembly's manifest definition with name 'Syncfusion.Tools.Windows' does not match the assembly reference.


i dont know which version of syncfusion they used while devoloping in vs2003..
am now installed the 4.6 version..

how to solve the issue??

2 Replies
AD Administrator Syncfusion Team August 9, 2007 11:28 PM UTC

Hi Janesh,

Please ensure that you are using version 4.x or above and also your licenses.licx file should contain only, 'Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'
Please follow the below steps,

1)Open the Assembly Manager utility from the location, Start --> All Programs --> Syncfusion --> Essential Studio 4.4.x.xx--> Utilities --> AssemblyManager
2)In the Action groupbox, select remove all versions and then click perform action. This will remove all the versions of Syncfusion assemblies installed in the given machine from the public assemblies folder and the GAC.
3)Then, in the Action groupbox, select Install version 4.4.x.xx and then click perform action. This will install the Syncfusion assemblies of version 4.4.x.xx in the public assemblies folder and the GAC. Your machine is now set to the version 4.4.x.xx
4)Delete Bin and obj folders of your project.
5)Open your project. Remove all the Syncfusion references and re-add them. Make sure they are all of version 4.401.x.xx
6)Now rebuild the project

Regards,
Swaminathan.

CE Calculer enligne December 15, 2025 07:21 AM UTC

This error usually happens when the Syncfusion assembly version referenced by the project does not match the version installed on your system. Since the application was originally developed in VS2003, it is very likely using an older Syncfusion version than the 4.6 version you installed.

Here are a few steps you can try to resolve it:

  1. Check the referenced version
    Open the project file or use the Object Browser / references list to see the exact version of Syncfusion.Tools.Windows it is expecting. VS2003 projects often target .NET 1.1, which newer Syncfusion builds may not support.

  2. Use the correct Syncfusion version
    Try installing the same (or very close) Syncfusion version that was available during the VS2003 timeframe. Newer versions (like 4.6) are usually incompatible with older .NET frameworks.

  3. Update references manually
    Remove the existing Syncfusion references from the project and re-add them from the installed Syncfusion folder. Make sure the Version, Culture, and PublicKeyToken match.

  4. Check the GAC
    If a different Syncfusion version is already in the Global Assembly Cache, it may cause conflicts. Remove older/newer conflicting versions from the GAC if needed.

  5. Binding redirects (if applicable)
    If the app targets a newer .NET version, you can try adding an assembly binding redirect in the config file, but this usually does not work well for very old VS2003 apps.

Think of it like a drone using the wrong firmware version—if the software doesn’t match the hardware, it simply won’t take off. Matching the exact Syncfusion version used during development is the key ffix here


Loader.
Up arrow icon