Re: Problem with C++ .Net
David Weir <[email protected]> Thu, 19 Jan 2006 09:41:45 -0330
| Newsgroups | gmane.comp.corba.orbacus |
|---|---|
| Organization | Object Oriented Concepts, Inc. - An IONA Company |
| Message-ID | <[email protected]> |
Hello Jean-Louis, On Thu, Jan 19, 2006 at 11:27:26AM +0100, Decoster Jean Louis wrote: > Hallo > > I need help concerning the migration from C++6.0 to C++-Net 2003. In > fact I receive exactly the same problem that I received with C++6.0 > before I update the compiler flag /MLd(Debug Single-Threaded) to > /MDd(Debug Multi threaded DLL). The recent days I have tried to find a > solution by modifying the flag of the project settings of my application > under c++.Net; but I got no solution. The system goes throw the same > code sequence and I receive the same "debug failed assertion" in the > module dbgheap.c > > (Using c++6.0 the Line Nr was 1044 and with C++.Net it is 1132). > > I need very urgently to get my system running with C++.Net; but I need > information's about the flag to be used to solve this problem or what is > going wrong with C++.Net? > > Flag status for C++6.0 > > /nologo /MDd /w /W0 /Gm /GR /GX /ZI /D "WIN32" /D "_DEBUG" /D "_CONSOLE" > /D "_MBCS" /Fo"Debug/" /Fd"Debug/" /FD /GZ /c > > Flag status for C++6.0 > > /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /FD /EHsc /MDd /GR > /Fp".\Debug/eLOckDb_Cons.pch" /Fo".\Debug/" /Fd".\Debug/" /W0 /nologo /c > /ZI /Gd > > I hope I will receive a response soon. Thanks a lot in advance > > And Regards > Jean-Louis In response to your previous question (from January 17th), Orbacus 4.3 should work with VC++ .NET 2003 (or VC++ 7.1) without any issues. Since you are migrating your application from VC++ 6.0 to VC++ 7.1, you need to make sure that you recompile both Orbacus and your application using VC++ 7.1. Also, you need to make sure that the compiler settings are the same for both. In particular, you need to ensure that if you specify a debug build for Orbacus then you also specify a debug build for your application, or vice-versa. We have seen issues like this here during our own testing, and it is usually the result of linking a test application against incorrect versions of the Orbacus libraries (i.e. libraries that have been built with different compiler options or a different version of the compiler than the test application). Cheers, Dave -- David Weir Team Orbacus - Your CORBA Source E-Mail: [email protected] WWW: http://www.orbacus.com _______________________________________________ OB-Users Mailing List - [email protected] http://mail.ooc.nf.ca/mailman/listinfo/ob-users Visit our support FAQ before you send a message. http://www.orbacus.com/faq/support.html