Error change framework 4.6 to 4.0 (XP)

Hi,

We did a change of framework from 4.6 to 4.0 to a XP.

We add reference dll to net 4.0 and them install the program. All well but when start the application chrash (attach a pic).

The reference on visual studio is "4400" and crash with "4460"


What happened?

thanks

Attachment: image001_4606e073.rar

3 Replies

AR Arulpriya Ramalingam Syncfusion Team April 4, 2018 03:40 PM UTC

Hi Mel, 
 
Thanks for using Syncfusion products. 
 
The reported issue will be occurred when the assemblies in the project are referred with different versions or mismatch versions in the assemblies. So, ensure that whether the PublickKeyToken for the assemblies are referred with same version. If the version of the assemblies is mismatching, please follow the below steps to resolve the issue, 
 
Suggestion 1 
  • Open you project in Notepad.
  • Check whether any key tokens are referring for the Syncfusion dlls. If yes, remove that key tokens of all Syncfusion assemblies. Please refer to the below code example.
  • Code example
<Reference Include=" Syncfusion.Tools.Windows, Version= 15.4460.0.20, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89, processorArchitecture=MSIL"/>   
<!--</Change the above code like as below for all the assemblies>-->   
<Reference Include=" Syncfusion.Tools.Windows "/>   
 
Suggestion 2: 
  • Select all the Syncfusion assemblies from project reference and open the property window (Alt + Enter) for selected assemblies.
  • Change the specific version as false using property window.
  • Now, clean and rebuild your project.
 
Please let us know, if you have any other queries. 
 
Regards, 
Arulpriya 



ME Mel April 5, 2018 09:39 AM UTC

Hi,

We delete all reference and update to 16.xxxx and the app crash again. The same error.

We search on all project the content: "15.4460" and don't appears on the files project. Only found one line on the .exe file but with machine code.

What can i do??

Thanks


AR Arulpriya Ramalingam Syncfusion Team April 6, 2018 11:49 AM UTC

Hi Mel,   
   
Thanks for the update.   
   
As we updated earlier, the reported issue occurs only when the assemblies are not installed properly or the referred assemblies are not included in the assembly location. So, we would suggest you to, ensure that all the dependent dlls of the assemblies which are included in the project. If some of the assemblies are missing, please install the assemblies in GAC by using assembly manager and refer to the below link to install the assemblies,   
   
   
Also, provide us the below details that will be more helpful for us to assist you further,   
  • Your machine configuration settings with .Net version.
  • Confirm us whether the GAC is installed in the testing machine or referring the dlls manually.
   
Regards,   
Arulpriya   


Loader.
Up arrow icon