The benefits and challenges of moving completely to a WPF project

Question

I have a project that I started as a WinForms application, since it was a format that I was managing at the time. Since then I started working in WPF and introduced some WPF UserControls (mostly grids) to my project and absolutely love them. The question that I have is there any real advantage for me, changing the project UI of my solution into a purely WPF project and getting rid of any WinForms? I am fully aware that each format is suitable for a specific environment, and you can’t give a final answer without knowing more details, but I would like to know the opinions of people, and if someone made a limit to convert the existing WinForms App into a WPF interface and any comments they made on this.

thanks

Answer 1

At the heart of the new WPF features is a powerful new infrastructure based on DirectX, a hardware-accelerated graphics API commonly used in advanced computer games. This means that you can use rich graphical effects without incurring the performance overhead that you suffered from Windows Forms. In fact, you even get advanced features such as support for video files and 3D content. Using these features (and a good design tool), you can create stunning user interfaces and visual effects that in Windows Forms would hardly be possible.

WPF improves features that appeal directly to business developers, including a significantly improved data binding model, a new set of classes for printing content and managing print queues, and a document function for displaying large amounts of formatted text.

But if you have done a lot of work on creating a Windows Forms application, you don’t need to port it to WPF to get access to new features like animation. Instead, you can add WPF content to an existing Windows Forms application or create a WPF application that will use your old Windows Forms content.

Link: Pro WPF in C # 2008: Windows Presentation Foundation with .NET 3.5, Second Edition