But this should never be the choice for new code. MFC has nothing to
offer a pure WPF application, because the library is married to its own
wrapper around the Win32 GUI.
If one has legacy apps written using MFC, and there is a need to insert some
WPF graphics in it, it could make sense to do it incrementally, instead of
doing a complete port of the MFC GUI part to WPF.
Hosting WPF content in an MFC GUI is just an option: the OP can choose what
to do in his particular case.
C++/CLI can be used for WPF, but without XAML support you'll be unhappy
trying to do so.
I completely agree with you on that. I consider C++/CLI a good tool just for
building some "bridging" layer between native code and managed code (like
exporting some native C/C++ library to the managed world, to use it in C#).
IMHO, native code should be done in C++, and for managed code C# is just
fine.
Giovanni