Errors in VS 2022 when loading various Telerik controls

[Geoff]

I have a WinForms .NET project running Telerik Version 2022.1.222.40 (I know its old but its what I have). Everything is working as expected and the application has no apparent problems at runtime.

After migrating to VS 2022 I am seeing various errors in the output. These errors appears to correspond with the loading of various Telerik components, the first of which is the theme but others include the Pageview control.

The following error is repeated at each of these times:-

Microsoft C++ exception: EEFileLoadException at memory location 0x000000ED451FB450.

Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.

Any help appreciated.

G

[Dinko | Tech Support Engineer]

Hi Geoff,

Thank you for contacting us.

Just to confirm, the reported error is not crashing the application and is only visible in debug mode in the VS output tab. I am not fully familiar with a C++ application, but as far as I am aware, the EEFileLoadException errors after migrating your .NET project are typically related to mismatched or outdated assembly references.

One option you can try is to close VS 2022. Navigate to the project folder and delete the bin and obj folders. Then open the project again in VS 2022 and rebuild it. Then test again if this error still appears. This will force VS to regenerate the build files and hopefully reset the settings so that this does not appear anymore. 

Regards,
Dinko | Tech Support Engineer
Progress Telerik

[Geoff]

Yes, that's correct, the application runs normally and the reported errors are only visible in the immediate window of VS 2022. Never the less I would like to try and resolve them if possible, its distracting and obfuscates real issues.

The main application interface and all dll's are written in C# with only the licensing dll written in C++. The licensing dll is not referenced directly by any of the application components and is calls to it are via [DllImport].

I have cleaned the folders you suggest but this has not had any impact. The first error is raised when the second line of the below code is called:-

var theme = new TelerikMetroTheme();
ThemeResolutionService.ApplicationThemeName = theme.ThemeName;

Thanks

G

[Dinko | Tech Support Engineer]

My guess here is that in VS2022, some assembly could not be correctly loaded or its dependencies. Is there an option to see a stack trace of the error?

What comes to my mind is to see the target build platform of the project. If it is x32, change to Any CPU and see if that will remove the error. Another option you can try is to update our assemblies to their latest version and see if that will remove the error. Apart from that, I am not sure what else I can suggest to remove this error.

[Geoff]

Sorry, I gave you some incorrect information, the first error appears when the code var theme = new TelerikMetroTheme(); is executed. The application build platform is x64.

These lines appear in the immediate window:-

Exception thrown at 0x00007FFDD415804A (KernelBase.dll) in [ApplicationName.exe]: 0x02345678 (parameters: 0xFFFFFFFF80000005).
Exception thrown at 0x00007FFDD415804A in [ApplicationName.exe]: Microsoft C++ exception: EEFileLoadException at memory location 0x00000054671FB2F0.
Exception thrown at 0x00007FFDD415804A in [ApplicationName.exe]: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
Exception thrown at 0x00007FFDD415804A in [ApplicationName.exe]: Microsoft C++ exception: EEFileLoadException at memory location 0x00000054671FB2F0.
Exception thrown at 0x00007FFDD415804A in [ApplicationName.exe]: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
Exception thrown at 0x00007FFDD415804A in [ApplicationName.exe]: Microsoft C++ exception: EEFileLoadException at memory location 0x00000054671FB2F0.

The stack trace looks like this when external code is shown:-

> [ApplicationName.exe]![ApplicationName].Program.Main() Line 25 C#
[Native to Managed Transition]
mscoreei.dll!_CorExeMain() Unknown
mscoree.dll!_CorExeMain_Exported() Unknown
kernel32.dll!BaseThreadInitThunk() Unknown
ntdll.dll!RtlUserThreadStart() Unknown

G

 

     

[Geoff]

Hmmm I think this is some .NET issue?

G

[Geoff]

Hi Dinko,

Well, how stupid do I feel!

I created another project as a test and I was unable to reproduce the issue which seemed odd. I then noticed that in the original project I had the "Enable Native Code debugging" option checked. This must have been left over from when we were stepping into the C++ licensing code earlier in the project lifecycle.

I have unchecked this option and all unexpected errors have disappeared.

Maybe this will help someone else at some point.

Thanks

G

[Dinko | Tech Support Engineer]

I am happy to hear that you were able to find the root of the error, and thank you for sharing it with the community. If you have any other questions, feel free to post them in our forum.