Click to See Complete Forum and Search --> : Need Help : Critical : C++ problems with using /CLR to move to managed compile


JohnFlyTN
June 8th, 2006, 09:17 AM
I've taken over an application (C and Win32).

I'm wanting to move it to managed code via the /clr compile switch in Visual Studio 2005.

The application utilizes many 3rd party DLL's as well as some "in house" written DLL's (managed and unmanaged). All but *one* work when I set the /clr switch and I can't figure out why.

The only DLL I have an issue with is for Crystal Reports (5 or 7 neither work) the dll loads but when I try to issue the crystal function PEOpenEngine() it returns failure(512). That error code doesn't help much as the online help states the error usually happens when you *forget* the call to PEOpenEngine().


Is there anything I can try to do to get this dll working in a managed C++/CLI application?