![]() When I add msvcrt.lib, I have to resolve conflicts that the libraries that are already included because it is using /MTd CRT. I already had the items "To convert managed DLL to mixed mode" except the including of msvcrt.lib. I believe that explains some of my issues. Last edited by garryMarshall January 31st, 2005 at 01:43 PM. For some reason the system does not like the loaded 'new' operator. This 'new' operator also causes the same error. Thank you so much for all of your help in resolving this issue. Is this correct or am I having another problem that I am missing? If this is correct, what 'new' operator must I include? I assume from this that I must need another 'new' operator than that was linked in. With the disassemby enabled, I can step through the above constructor and when it calls the "new" operator, I get the "System.StackOverflowExecption" unhandled exception error. M_pUnmanagedConfig = new UnmanagedConfig() The managed class constructor is as follows: When I run the debug code, the C# code calls the Managed class constructor which in turn calls the unmanaged class constructor. ![]() Note that I now have no "Additional Dependencies" and no "Ignore Specific Libraries".īy defineding my Interface DLL to be /MTd with NO other Linker Dependencies libraries, it compiles and links with no errors. Since I can not change the Legacy C++ lib, I must use only static linking libraries in my interface DLL code which is also defined as using the /MTd RTC. I understand now that I can NOT mix the defining of /MTd (multithreaded static linking) and then linking in the msvcrtd.lib which is a dynamic link library. Legacy C++ lib (runtime library: /MTd) can not be changed Interface DLL which includes: (DLL /MTd) (one DLL with two classes)ģ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |