C++ MFC vs .NET?

Question

My colleagues are using Visual Studio 2002 and uses the C++ MFC. I am developing in C #.

It has not been any problems before, but now questioning our customers if we really should develop in different environments. My colleagues think (of course) that I should move to C++ MFC. I think that they can use .NET instead of MFC.

Is there any point to learn the MFC? It feels a bit outmoded, or am I wrong? What are the arguments against and for .NET compared with MFC?

Edit:

We are developing process systems and assistance applications for the nuclear industry. The main application is an emulator that emulates an old computer system and uses C++/MFC. It is very time critical, maybe the core should it still be in native C++. But the GUI to the emulator and all surrounding applications are not particularly critical.

And is there any real reason that you should replace the existing MFC application?

user_9778277 · Answer

Oh man. I know I am super late to this party, but as someone who has written in C and pure Win32, and then the bulk of his career in C++/VC/MFC, writing in C# and WPF is a PAIN!! I know I am new, but I'm forcing myself to write this little application in C# because I want to be more comfortable with C#/.NET and WPF. While it is nice that I was able to make the UI a sleek black easily, the time it is taking for me to define a menu, when in MFC I would have created the menu resource, adding the menu items and then added event handlers to them with EASE! This is drudgery. I like C# as a language, but I would love this SO much better if I could define everything like I can in the resource editor with MFC/Windows AND add the ability to jazz up the UI elements like in WPF.

C++ MFC vs .NET?

11 Answers