What is the difference between WPF and WinForms?

WPF can utilize hardware acceleration to some degree, but that is expected to improve over time.

Also, because of XAML, you have more options for "doing stuff", declarative vs. programmatic, or a mixture of both.

Microsoft no longer does active development on WinForms, they are strongly pushing WPF, and for good reason.

WPF allows for much easier "resolution agnostic" designing. To achieve that in WinForms, it is a lot more work.

The MVVM pattern was already mentioned in one of the comments, this allows one to do real unit testing vs. GUI-based testing on your code, that is a big win, in my experience.

Nobody mentioned about better testing capabilities of the WPF applications (if they are written in the correct way, for example based on the MVVM pattern).

A

Anywhere Execution due to XAML.

Can be used as WinApp, WebApp, Mobile.

Whereas WindowsForm Internal UI representation is in C#.

B

Binding -->Simple object to object data transfer.

C

Common look and feel(Styles) -->can define look and feel styles commonly and use it for bunch of controls.

D

Directive Programming -->Binding objects in XAML.

E

Expression blend and Animation-->WPF uses DirectX, and DirectX can be used for animation.

F

Faster Execution(Hardware Rendering)

WPF internally uses DirectX (Hardware rendering) while Winform internally uses GDI (mostly uses Software rendering).

There are two ways by which a computer renders display on monitor.

1) (CPU) Software rendering -->In case of CPU rendering ,the CPU drives the whole logic of rendering display on monitor.CPU also does other operations like running applications,performing memory management,running OS. So on top of it its extra load to display things on monitor.

2)(GPU) Hardware rendering -->Its Specialized kinda processor, specifically meant for rendering and display faster on monitor.

Now in WPF, this rendering is further optimised in

>Tier 0 mode (Software rendering) uses DirectX7 internally,

>Tier 1 mode (Partial Hardware rendering) uses DirectX7 to DirectX9 internally,

>Tier 2 mode (Hardware rendering) uses DirectX9 internally. 

G

Graphic Independence (DIP) -->Means resolution independence

Resolution --> Total number of pixels that fits into screen/monitor

Pixel --> Simple dot on screen.

Windows form uses pixels as a measurement unit, so when pixel changes then win forms has to adjust itself that means we have to write logic for it.

But WPF does not use pixels as a measurement unit but uses DIP(Device independent pixels)

1 DIP = 1/96th of the inch.

At last Testing --> Better unit testing with use of MVVM pattern.

• The single most important difference between WinForms and WPF is the fact that while WinForms is simply a layer on top of the standard Windows controls (e.g. a TextBox), WPF is built from scratch and doesn't rely on standard Windows controls in almost all situations.

• A great example of this is a button with an image and text on it. This is not a standard Windows control, so WinForms doesn't offer you this possibility out of the box. Instead, you will have to draw the image yourself, implement your own button that supports images or use a 3rd party control. With WPF, a button can contain anything because it's essentially a border with content and various states (e.g. untouched, hovered, pressed).

check this article it will help you: https://www.wpf-tutorial.com/about-wpf/wpf-vs-winforms/#:~:text=The%20single%20most%20important%20difference,controls%20in%20almost%20all%20situations.