SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and iOS Chart & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
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!
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!
Please login first to submit.