How many of you are working on a new MFC professional project?

[Arjay]

WinForms are now being replaced by WPF, which requires more code maintenance, than a MFC project.

Why do you believe this to be the case?

[Ajay Vijay]

I mean the WPF technology is out. For excellent GUI, many are thinking of migrating from Windows Forms applications to rich WPF applications. Since, there are class hierarchy changes, and some stuff like data binding must be put in .XAML file - it obviously needs more of code changes, than required in upgrading MFC (like group-view in list control, requires less change).

[JohnW@Wessex]

We use MFC in all new applications for a number of reasons.

1. Using C# for the UI has been raised now and then, but we all know C++ & MFC well and have little to no experience of C#
2. Our GUIs are simple enough for WPF or Forms to not have any real advangtage over MFC
3. Splitting the code into separate C++ processing and C# GUI sections just adds complexity but no real benefits for us.
4. Over the years we've built up a library of sub-classed MFC components that have an STL interface and add functionality common to most of our applications.