By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,194 Members | 811 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,194 IT Pros & Developers. It's quick & easy.

MFC and Win 32

saranjegan
P: 51
dudes:
whats the difference between MFC application and win 32 application

if MFC was developed with win 32 API, can we convert a win 32 application to MFC application
Mar 19 '07 #1
Share this Question
Share on Google+
4 Replies


P: 39
From what I can remember, developing under Win32 is a lot like developing in C/C++. If you want something done you can do it but you are on your own to remember what calls need to be made prior and afterwards. So MFC is a derivative of the Win32 API, making GUI applications a bit easier to use and develop with. As to your other question, of course; however, my experience with Win32 API is limited so I am not completely sure if there is anything special needed.
Mar 19 '07 #2

Banfa
Expert Mod 5K+
P: 8,916
Basically WIN32 API is the bottom level, everything else MFC or anybody elses class library for that matter ends up making WIN32 API calls. These are calls directly into the Windows DLLs.

MFC is a set of classes that wraps the WIN32 API in order to make application development easier. However the internals of MFC are rather bloated so it also tends to make applications a bit slower.

In theory you could convert a WIN32 API application to MFC, however I can not really think of any advantage of doing that and it is not a trivial process. You would probably find youself creating a new MFC application and then adding handlers and copying small chunks of code from your old application to the new one.
Mar 19 '07 #3

saranjegan
P: 51
Basically WIN32 API is the bottom level, everything else MFC or anybody elses class library for that matter ends up making WIN32 API calls. These are calls directly into the Windows DLLs.

MFC is a set of classes that wraps the WIN32 API in order to make application development easier. However the internals of MFC are rather bloated so it also tends to make applications a bit slower.

In theory you could convert a WIN32 API application to MFC, however I can not really think of any advantage of doing that and it is not a trivial process. You would probably find youself creating a new MFC application and then adding handlers and copying small chunks of code from your old application to the new one.
oh..i can understand your reply thnks for it,can u suggest me some tutorial or links for it so i can gear up,thnks for your time
Mar 20 '07 #4

saranjegan
P: 51
From what I can remember, developing under Win32 is a lot like developing in C/C++. If you want something done you can do it but you are on your own to remember what calls need to be made prior and afterwards. So MFC is a derivative of the Win32 API, making GUI applications a bit easier to use and develop with. As to your other question, of course; however, my experience with Win32 API is limited so I am not completely sure if there is anything special needed.
oh..i can catch you thanks for your time
Mar 20 '07 #5

Post your reply

Sign in to post your reply or Sign up for a free account.