ImageEn for Delphi and C++ Builder ImageEn for Delphi and C++ Builder

 

ImageEn Forum
Profile    Join    Active Topics    Forum FAQ    Search this forumSearch
Forum membership is Free!  Click Join to sign-up
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 ImageEn Library for Delphi, C++ and .Net
 ImageEn and IEvolution Support Forum
 [IEvolution] mismatching dlls on install
 New Topic  Reply to Topic
Author Previous Topic Topic Next Topic  

SteveGriffiths

USA
1 Posts

Posted - Mar 14 2012 :  12:22:24  Show Profile  Reply
I have created an active X control that uses IEvolution. When I run the installer on the same box I installed IEvolution it is fine. When I run the installer on another box I get the following error:

"iecore.dll (1038) and IEvolution2.dll (1045) versions mismatch!"
I do not see iecore.dll in my deployment project.

My goal is to have the Active X download from a website - it allows user local scanning and uploading. I am replacing a Delphi 7 / Imagen version with s Dot Net 2010 version.

All help appreciated.

Thanks

Grif

fab

1310 Posts

Posted - Mar 14 2012 :  12:49:56  Show Profile  Reply
iecore.dll is required by IEvolution2.dll. You have to put it in the same directory of ievolution2.dll or in the PATH.
Go to Top of Page

jez

20 Posts

Posted - Jun 04 2013 :  03:23:58  Show Profile  Reply
I am seeing the same thing in a VB.net application and having no success fixing it. Have been using IEvolution2 for a while and have never had this problem before. I get the following message twice on application startup.

iecore.dll(1040) and IEvolution2.dll(1045) versions mismatch

The files are both in the same directory as the application.exe and are from the same Evolution2 downloaded zip file.

jez
Go to Top of Page

xequte

39052 Posts

Posted - Jun 05 2013 :  02:45:46  Show Profile  Reply
Hi Jez

Have you checked your system path (e.g. Windows folders) for other instances of these DLL's?



Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
Go to Top of Page

jez

20 Posts

Posted - Jun 05 2013 :  08:21:33  Show Profile  Reply
Yes I did, but it's my understanding that the directory holding the .exe is the first place the system looks so it shouldnt matter. I fixed it in the end when I noticed the Evolution2 assembly reference was in the GAC (global assembly cache). When I removed this reference and added one direct to the Evo2 assembly, the message went away. So maybe there is an old version in the GAC though I'm not sure how it would have got in there.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
Jump To: