| T O P I C R E V I E W |
| brandonbrown |
Posted - Jun 19 2026 : 05:51:10
I've finally upgraded to IEvolution 14.
In Visual Studio 2022, I was loading the toolbox controls from IEvolution4.dll and it does load, shows in the toolbox, but when selecting it and creating an instance on the form, it crashes Visual Studio 2022. I did try IEvolution2.dll in the IEvolution32 directory also since I am writing a 32-bit app because of some old TWAIN drivers that are only supported in 32-bit. That didn't work either.
I thought it might be VS2022, so I loaded Visual Studio 2019, and the same behavior happened.
I tried uninstalling and reinstalling version 14.0, nothing worked.
I tried cleaning out the toolbox cache, and other basic troubleshooting steps and nothing wored so I uninstalled IE14.0.
I then installed my old version 10.5.0 and it worked in both VS2022 and VS2019.
Do I have a corrupted installed of IE14.0? Any others experiencing this? |
| 9 L A T E S T R E P L I E S (Newest First) |
| xequte |
Posted - Jul 14 2026 : 20:38:13
Hi Brandon
Please see my latest email...
Nigel
Xequte Software
www.imageen.com
|
| brandonbrown |
Posted - Jul 06 2026 : 14:16:32
I confirmed my version of IEvolution 14's install on 2 different machines with three different versions of Visual Studio. All allow the IEImage to be dropped on the form, all also hung/crashed Visual Studio, no matter the version when using the IEMulti.
I tried to add the IEMulti at run time, but that looks like it will be a lot of effort.
For now, I uninstalled 14.0 and went back to 10.5.0 B_71228.
The version I had for 14.0 was 14.0 D_80138.
Using Visual Studio 2026, I am trying to upgrade a scanning app I had possibly using TWAIN32 scanners, so I loaed IEvolution4.dll in the 32-bit directory for both the reference and in the toolbox edition.
Let me know what you find out and thank you for looking into this! |
| xequte |
Posted - Jul 05 2026 : 17:55:18
Hi Brandon
My partner will need to investigate this further.
IEvolution2 is for legacy .NET. 32bit/64bit are for creating 32bit and 64bit apps respectively.
Nigel
Xequte Software
www.imageen.com
|
| brandonbrown |
Posted - Jul 03 2026 : 05:13:59
It just crashes whatever version of Visual Studio you are on. I tried the latest first, 2026, then 2022 and from what I read, they are native 64-bit, so I went back and installed 2019.
A little bit more info, the IEViewer will load from the toolbox onto the form, IEMulti won't. I am not sure if I have a corrupted install or something, but I made sure I cleaned off any other iecore.dll, etc as I stated above.
What is the difference between IEvolution2 and IEvolution4? 32-bit vs 64-bit?
|
| xequte |
Posted - Jul 02 2026 : 16:30:20
Thanks Brandon, is it an Access Violation error message that you encounter?
Nigel
Xequte Software
www.imageen.com
|
| brandonbrown |
Posted - Jul 02 2026 : 15:14:36
Nigel,
When I am creating a new project, is the correct steps for a 32-bit app (any CPU) this:
1. Project->Add Reference
Then select c:\Program files\iEvolution\IEvolution32\Ievolution2.dll
2. Right click in the toolbox, Choose Items, Click Browse and select:
c:\Program files\iEvolution\IEvolution32\Ievolution2.dll
I'm just wondering as the crashing is happening when I put a control on a form.
I unloaded IEvolution 14, loaded version 10.5 and these steps work.
I also tried IEvolution4 in both places also, same behavior. |
| xequte |
Posted - Jun 23 2026 : 23:51:51
Nice one Brandon 
Nigel
Xequte Software
www.imageen.com
|
| brandonbrown |
Posted - Jun 23 2026 : 10:00:38
Thank you as always for your quick reply! I had to go find the other iecore files and delete them and reinstall.
It is working now within VS2022.
Thank you! |
| xequte |
Posted - Jun 22 2026 : 20:30:36
Hi Brandon
We're not aware of any issues, and it is working as expected when we test it here.
Do you see any errors or A/V exceptions? Are you able to forward us a simple Visual Studio application to test here?
Nigel
Xequte Software
www.imageen.com
|
Search
