MFC Windows Development, is it a waste of time?

Translate This Page

MFC Windows Development, is it a waste of time?

  • Comments 4

I am conflicted about MFC Windows Development, other than keeping the tools designers focused on VC++, is it a reasonable expectation that anyone would support the inefficiencies in developing UI with VC++.  It has been long known that C++ for higher level programming is, well, just a waste of money.  If I was a manager and someone suggested to me that the best way to build a UI based app would be to use VC++ or C++, I would have to question the worker’s motivations and intellectual capabilities.

I could be wrong, I am sure someone will let me know why MFC and VC++, or C++ is more efficient, but really, when I look at iPhone and the awful development system that Apple has supplied it’s developers with Objective C, I am surprised that managers, artists and others don’t get out the torches and storm the development labs.

Now, I moved for some reason from VB.NET to C# and never really realized why.  But unless I am doing game design, I rarely touch VC++ anymore.

If you want to evaluate if I am right or wrong, you might want to start off by installing VC++ by downloading and installing the VC++ Express:

Starting tutorial:

MFC isn’t included in the Visual Studio VC++ Express 2010, you will need to install the Visual Studio 2010 Pro or Ultimate to utilize the MFC.  If you are a student you can get the Professional via Dreamspark and Ultimate through MSDNAA.

See my other blogs at:

Leave a Comment
  • Please add 3 and 6 and type the answer here:
  • Post
  • "It has been long known that C++ for higher level programming is, well, just a waste of money."

    Where do you get that from?

    You should have a talk with the Windows, Office, and Windows Live teams then!

  • Good point Native, the remark could easily be mistaken, or actually the remark was just wrong.  Let me explain:

    1. I am on the customer side of things, so I have not heard that the users of Office have a tendency to break out C++ to add functionality to Office products.  C#, VB.NET or VB for applications would used to do that.

    2. The Office team has well developed processes to use VC++, not the case with most developers.

    As to where did I get the comment you commented on?  Respectfully Native, I made it up.  If you notice, when I use other people's stuff I reference it. Apologies if there was any confusion on this issue.

    Thank you for the nice comment and the strong questioning of my statements.  One should always question everything and question it aggressively.  Keep it up, it is a good thing.

  • My apologies, my previous comment was quite rude.

    But I find it difficult to read that high level programming in C++ is a waste of money when you see so much software written in that language (Internet Explorer, Photoshop, etc.).

    On the other hand, I agree with you concerning MFC, it should no longer be used to write new software. There are some modern libraries and framework available on the market. (and there are strong signs on the VC++ blog/Channel 9 that Microsoft is working on some new libraries and tooling related to native - and espacially UI - development).

  • Native, Didn't read it as rude, it was a good comment.  Actually, like a lot of writers, I used what I think of as the "Mad" magazine approach to headlining: Say something bombastic and then attempt to support it.

    I think that the VC++ folks need a wake up inside of Microsoft, there likely should be a branch from the "standard based" language and a way to develop using modern tools like a C# with privileges so to speak.

    Also, the VC++ folks really need to get their act together with respect to C, since hardly anyone understands that C can be developed using VC++ Express, or the VC++ Pro/Ultimate, which is a shame.

    Finally, the definition of rude comments (and yours were not): Anything with curse words, and curse words are defined by the George Carlin 7 words that can't be said on the radio.

    Otherwise, feel free to fire away.

Page 1 of 1 (4 items)
Generic Content

Legal Note:

  1. The author, Sam Stokes, is an employee of Microsoft
  2. There is no guarantee that anything I write is correct, I do try to make sure that what I write is correct.
  3. Use anything written in this blog at your own risk
  4. Test what I write about before using the information
  • Sometimes posts will disappear because I realized that they really don't fit with the total chaos of what I write about
  • Links are tested and available on date of publication, what others do with their links are out of my control

Restrictions:

  • Whatever I write on this blog is unedited by management or anyone, which should be obvious from the randomness of the blog.  I simply write about things I like.
  • Microsoft does not restrict me in anyway, so I generallyblather about whatever I want to.
  • For personal reasons I will not write about:
    • Company confidential stuff, mainly because Microsoft is more transparent than any company I have ever worked for.
    • Other people unless they give me permission to write about them