![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#11
| |||
| |||
|
|
On Mar 20, 3:00 pm, "Ben Voigt" <r... (AT) nospam (DOT) nospam> wrote: It appears to be a loader lock Which version of C++.NET are your assemblies? Managed Extensions for C++ (VC2003) has known loader lock bugs that microsoft won't fix. Use C++/CLI (VC2005) instead. Eyal Safran.- Hide quoted text - - Show quoted text - Do you know if by compiling my Managed C++ dlls in VC2005, but still in .NET framework 1.1, will solve my loader lock problem? Eyal Safran. |
#12
| |||
| |||
|
|
"esafran" <e... (AT) mokedor (DOT) com> wrote in message news:1174402256.204704.116510 (AT) d57g2000hsg (DOT) googlegroups.com... On Mar 20, 3:00 pm, "Ben Voigt" <r... (AT) nospam (DOT) nospam> wrote: It appears to be a loader lock Which version of C++.NET are your assemblies? Managed Extensions for C++ (VC2003) has known loader lock bugs that microsoft won't fix. Use C++/CLI (VC2005) instead. Eyal Safran.- Hide quoted text - - Show quoted text - Do you know if by compiling my Managed C++ dlls in VC2005, but still in .NET framework 1.1, will solve my loader lock problem? Eyal Safran. No, this won't work, if you can't fix the "OS loader lock" issue by one of the resolutions as mentioned in the article (Initialization of Mixed Assemblies ) pointed to by Ben, then you are out of luck and you will have to move forward. Willy.- Hide quoted text - - Show quoted text - |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |