Hi,
I have a very strange problem. When starting my application with referenced SciChart DLL in “Release” mode all works fine.
If I start in DEBUG (Any CPU) mode, I get an error when loading the DLL’s and the application crashes:
“‘SeverVisual.exe’ (Managed (v4.0.30319)): Loaded ‘p:\Projects_ITS\project_sever\SeverVisual\bin\Debug\Abt.Controls.SciChart.Wpf.dll’
First-chance exception at 0x7550b9bc in SeverVisual.exe: Microsoft C++ exception: EEFileLoadException at memory location 0x00148e74..
‘SeverVisual.exe’ (Managed (v4.0.30319)): Loaded ‘Abt.Controls.SciChart.Wpf&’
First-chance exception at 0x7550b9bc in SeverVisual.exe: Microsoft C++ exception: EEFileLoadException at memory location 0x0014ab60..”
In Debugx86 the error message also appears in the output window, but the application can start.
Thanks for help!
- dewulf asked 11 years ago
- You must login to post comments
I did a bit of googling on EEFileLoadException and found this: http://stackoverflow.com/questions/93770/eefileloadexception-when-using-c-sharp-classes-in-cwin32-app
Sounds to me like you’re referencing SciChart from a C++ application? If so then a few things might be amiss. It might be the location of the file, or also could be an image mismatch between x86/x64 on the C++ side and the AnyCPU compilation of SciChart.
From memory (it’s been a while since I worked on mixed managed/native apps), if the C++ was compiled as x86 then the managed would have to be compiled as x86 too.
Anyway, let me know what you come up with – if you can help us pinpoint the issue, we will do our best to fix it!
Andrew
- Andrew Burnett-Thompson answered 11 years ago
-
I also found some of these error descriptions about referencing from C++. But thas is not in my case. It is a clean C# WPF project. I'm actually thinking the problem is related to the Npgsql.dll that I'm referencing. Application crashes when doing some databsse related operations. I have to investigate once more.
-
Ok. My hunch is mismatch between x86 (or x64) compiled image and AnyCPU of .NET. If you can find out more it may be that we just need to recompile for x86/x64 (no more than a compiler switch in .NET). Best regards, Andrew
- You must login to post comments
Please login first to submit.