Re: CodeJock MFC products now 50% off thru end of October 2007

Hi Ajay,

I think MFC still has some life left in it. I tried doing, as you say, and creating a desktop application using .NET. It worked, but I couldn't get the performance on large data arrays that I needed. It was also slow updating controls (like the list control). C# is a nice alternative to VB for me since it is so close to cross over from C++, but I don't agree that it makes "no sense" to do native applications. I think I'll believe in the promise when all of MS Office is managed code ...

Tom

"Ajay Kalra" <ajaykalra@xxxxxxxxx> wrote in message news:CD5F6A0B-E3F5-454F-BC52-54A8A53EDA9B@xxxxxxxxxxxxxxxx

"Somebody" <somebody@xxxxxxx> wrote in message news:TrgOi.1804$5b2.913@xxxxxxxxxxxxxxx

"Ajay Kalra" <ajaykalra@xxxxxxxxx> wrote in message news:DC56C202-5C22-4565-880D-F8F5946AD211@xxxxxxxxxxxxxxxx

"Somebody" <somebody@xxxxxxx> wrote in message news:PrcOi.101$Ge3.46@xxxxxxxxxxxxxxx
Whys that?

The majority of desktop software is written in C++, not .NET.

Thats no longer true for new apps. All the legacy continues to be what it was C++ etc but new apps are predominantly .Net.

For web applications, yes. Honestly, I'm not trying to debate you on this. If I was to write a brand new desktop application today, I would certainly push for C++/MFC as .NET makes little sense for the desktop area.

I am not talking about web apps. IMO, in today's world it makes absolutely no sense to not use .net for destop apps. I did MFC for over 10 years and have been doing .Net for over a year. The difference is like day and night. I wouldnt do it on any legacy C++/VB app.


Why just last week, I was working on a desktop app that the company migrated to C#. Not for any particular reason, just because they wanted to be cutting edge. I was fixing a bug and for the *MILLIONTH* time, I had to call a native function. It took close to 100 lines of code to do so after converting all the data back and forth. Yeah, thats really efficient :).

Same can be said for MFC or any platform. This is nothing to do with what .Net can or cannot do.

---
Ajay


.

Relevant Pages

  • Re: Forms and VC++
    ... programmers. ... pretty well forced into giving them an introduction to MFC. ... capability is easier to use than MFC. ... etc. - .NET has garbage collection of course so your C++ apps will no longer ...
    (microsoft.public.vc.language)
  • Re: Followup: Native win32 apps still require .NET runtime?
    ... >any thought I had of compiling my MFC app with CLR. ... I've written lots of MFC apps but haven't been tempted to recompile ... it may fix the bug I've seen, so I don't want to do that. ... I was originally skeptical someone told me about the DLL problem. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Unicode setting question
    ... and yet WinForms has long ago overtaken MFC for writing Windows GUI ... The mass-deployed consumer apps that I typically write ... I am skipping WinForms in favor of WPF. ...
    (microsoft.public.vc.mfc)
  • Re: MFC future?
    ... but the IDE in 2003 is not as productive for C++ (especially MFC) ... I don't write dialog-based apps, ... I write SDI doc/view applications ... doesn't restrict you (though, as I said, many of us feel that the VC6 IDE ...
    (microsoft.public.vc.mfc)
  • Re: My Review of MFC Beta
    ... really want Windows apps to be managed anyway, as security is better. ... Instead of hoping for an MFC miracle, I'll be working towards a general ... Web-centric apps will also move the world to a subscription model instead ...
    (microsoft.public.vc.mfc)