how can use MFC in a non MFC win32 project
-
what steps i will have to do before i could use MFC in a win32 non mfc project. Unmanaged in a .NET world
-
what steps i will have to do before i could use MFC in a win32 non mfc project. Unmanaged in a .NET world
Why????? Isn't much simpler to use Win32 source files in MFC project? Robert-Antonio "A flower walked around a meadow. She saw a beatiful human and plucked off his head."
-
Why????? Isn't much simpler to use Win32 source files in MFC project? Robert-Antonio "A flower walked around a meadow. She saw a beatiful human and plucked off his head."
Well i know it can be that way aswell , but i am more intrested in this cauz i have quite a few win32 projects (not written by me) and i want to extend them with MFC . So still my question is same Unmanaged in a .NET world
-
what steps i will have to do before i could use MFC in a win32 non mfc project. Unmanaged in a .NET world
-
Don't you just include the appropriate MFC header files (see StdAfx.h of standard MFC project)?:cool:
If I Include all MFC Headers file it gives in linking error "void * __cdecl operator new(unsigned int)" (??2@YAPAXI@Z) already defined in LIBCMT.lib(new.obj) when compiming in MFC Statis Library mode Unmanaged in a .NET world
-
what steps i will have to do before i could use MFC in a win32 non mfc project. Unmanaged in a .NET world
Belive me its a pain to convert win32 application to MFC application its not as easy as including few header files and thats it. Besides ur current win32 logic may stop functioning or give unexected error coz both are off different architecture. and besides there nothing much that MFC can do that win32 can't. :)
MSN Messenger. prakashnadar@msn.com
-
If I Include all MFC Headers file it gives in linking error "void * __cdecl operator new(unsigned int)" (??2@YAPAXI@Z) already defined in LIBCMT.lib(new.obj) when compiming in MFC Statis Library mode Unmanaged in a .NET world
-
Belive me its a pain to convert win32 application to MFC application its not as easy as including few header files and thats it. Besides ur current win32 logic may stop functioning or give unexected error coz both are off different architecture. and besides there nothing much that MFC can do that win32 can't. :)
MSN Messenger. prakashnadar@msn.com
Well I have solved this issue 1.First of include all headers files present in a MFC project stdafx.h 2.Go to Project --Settings ---General and select either MFC in shared library or MFC in static Library Option 3.In static library option it will give the already defined linking error to solve this issue follow this link and do the apropriate steps as given in this link http://www.as-ltd.co.uk/cgi-bin/support/faq/XLPFAQ004.htm after it include stdafx.h where u want to use MFC. Unmanaged in a .NET world
-
what steps i will have to do before i could use MFC in a win32 non mfc project. Unmanaged in a .NET world
-
#include or #include After that, the MFC classes should be available to your application.
-
Well I have solved this issue 1.First of include all headers files present in a MFC project stdafx.h 2.Go to Project --Settings ---General and select either MFC in shared library or MFC in static Library Option 3.In static library option it will give the already defined linking error to solve this issue follow this link and do the apropriate steps as given in this link http://www.as-ltd.co.uk/cgi-bin/support/faq/XLPFAQ004.htm after it include stdafx.h where u want to use MFC. Unmanaged in a .NET world