INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

When to use the different VC++ projects?

When to use the different VC++ projects?

(OP)
I'm trying to understand when it is appropriate to use the different types of C++ project in MS Visual Studio.
For example, Win32, MFC, Windows Forms application (Is it Managed?).

If the Windows Forms Applications is managed, which give it the form designer like VB & C#, why use Win32 or MFC??

Is there a book on Managed Visual c++?? Most that I have looked at do not seem to cover managed C++. They seem to focus on basics and MFC. I need more of an intermediate book.

Regards

RE: When to use the different VC++ projects?

If it is a non-deliverable program that you always run in the debugger, it doesn't matter what you choose.  It depends a lot on your deliverables

win32 will need C runtimes if linked as multithreaded dll.  This is good for console programs or programs using the SDK or WTL.

mfc will need C runtimes and MFC runtimes if linked as multithreaded dll requiring MFC dlls.  You can also link as static but the executable will be huge.

winforms will need .net framework installed.  You may end up with a 100K program but you will need 20Mb of .net framework.  If installed on a system which is not as up to date as yours, you may get side-by-side problems.

WTL is the same as MFC except that it doesn't have a massive overhead of unwanted routines so the executables end up a lot smaller.  There are a lot of old stuff is still MFC based so M$ can't get rid of it.  MFC and WTL are built on top of the SDK so they can't get rid of that either.  Only problem is you probably need to try a 2nd hand bookshop to find material on MFC.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close