Comparison between MFC, Winform, and WPF

 

The local code generated by MFC is naturally fast. However, the message loop slows down the display speed on the interface.

Winform encapsulates win32 APIs for multiple P/invoke operations (most of which are encapsulated using p/invoke operations), which is slow.

Wpf is a new model. It no longer uses win32 models. It creates models by itself. dx is used as a new display technology to directly access the driver and speed up running. However, this model, you need to support the dx 9 video card with high hardware requirements (Can you find that the modern machine does not support dx9 ?)

In terms of development efficiency, MFC <WPF <winform

Although the execution efficiency of the MFC development interface is high, the development efficiency is low. As for current project development, time and development efficiency often determine the success or failure of the project, unless there are special requirements, otherwise, try to avoid using mfc for development. MFC is just a weak package.

Development Cost, MFC> wpf> winform

The development cost of using MFC is too high, which requires higher developer capabilities. As a customer service, the lower the development cost, the better. The developer certainly wants to make more money, the better, this is also a big reason for the decline of MFC.

In terms of interface execution efficiency, MFC = WPF> winform

As the performance of computer hardware increases and the popularity of multi-core CPUs, the gap between them will become smaller and smaller.

Development flexibility: wpf> MFC> winform

Appearance: Wpf> winform> MFC

In this case, it is extremely difficult to develop a gorgeous ui under MFC. You may say that you can use controls, but commercial development controls are charged !! Wpf can easily make ui effects like vista. I don't know what year or month the mfc should write this effect.
In this way, the value of MFC is lower. The efficiency and beauty are not as good as Wpf, and the development efficiency is not as good as winform. It is expected that within 10 years, with vista replacing xp, mfc will exit the stage of history.

Memory usage: wpf> winform> MFC

The defect of wpf will be ignored as computer hardware performance improves.

Scope of use: wpf> MFC = winform

As we can see from the above: WPF is a great trend to replace winform and MFC. From the perspective of future net development, MFC will only become a classic type and will be used as a technology for developers to learn, winform and WPF will coexist, but will eventually be replaced by WPF, and eventually achieve the unification of desktop and browser applications.