G
Guest
I have created a mixed mode (managed + native) application that links to a
mixed mode dll. It runs fine on all XP machines with Visual Studio .Net
installed, but on other machines with the .Net framework installed but not
Visual Studio, it displays a pop-up window entitled "Common Runtime Debugging
Services," and the unhelpful message: "Application has generated an exception
that could not be handled." This happens when the application gets to the
managed-code wrapper of a function (C++) that initializes the dll
(__crt_dll_initialize) .
The error is triggered just before it enters the crt-initializing wrapper
function. It won't display a message-box window placed within the function
but before the initialization. Try-catch does not catch the error.
Depends.exe show no missing or problematic module. The error also is
triggered when 0 is assigned to a pointer to a managed class of the dll.
Any suggestion would be appreciated.
mixed mode dll. It runs fine on all XP machines with Visual Studio .Net
installed, but on other machines with the .Net framework installed but not
Visual Studio, it displays a pop-up window entitled "Common Runtime Debugging
Services," and the unhelpful message: "Application has generated an exception
that could not be handled." This happens when the application gets to the
managed-code wrapper of a function (C++) that initializes the dll
(__crt_dll_initialize) .
The error is triggered just before it enters the crt-initializing wrapper
function. It won't display a message-box window placed within the function
but before the initialization. Try-catch does not catch the error.
Depends.exe show no missing or problematic module. The error also is
triggered when 0 is assigned to a pointer to a managed class of the dll.
Any suggestion would be appreciated.