Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is learning WinForms worthwhile? Is it outdated?

Tags:

c#

.net

winforms

I just completed two WinForm applications as part of an intensive course. Just wondering about the technology overall... should I move onto something new, or is WinForms still viable for the future?

like image 862
RedEye Avatar asked Apr 28 '10 20:04

RedEye


People also ask

Should I still use WinForms?

Compared to WPF, WinForms has much better design-time experience in Visual Studio. This itself is enough to choose WinForms. This is my experience with WinForms and WPF. However, you can choose the appropriate technology as per your requirements.

Is Windows form still 2022?

The latest version of Windows Forms is for . NET 6 using Visual Studio 2022 version 17.0. The . NET Framework 4 implementation that's supported by Visual Studio 2022, Visual Studio 2019, and Visual Studio 2017.

Is WinForms dead?

As we mentioned above, WinForms is still available but the status of “maintenance mode” likely means it has no long term future. As time passed by, especially in the last 5-10 years, new tools continued to mature and rise in popularity, and each one of them offered many powerful features.

What will replace WinForms?

Universal Windows Platform. Both Windows Forms and WPF are old, and Microsoft is pointing developers towards its Universal Windows Platform (UWP) instead.


1 Answers

I would say that Windows Forms is great for form-driven applications. WPF/Silverlight is great for animation and graphic-driven applications.

If you need to do some utility work or make a tool, I don't see why Win Forms can't serve that purpose. WPF might be overkill unless you really want it to look pretty. Plus with WPF you have to learn XAML which isn't as easy or intuitive as working with Win Forms designer.

If you are a web developer or designer, working in WPF might seem more similar to designing a web page because you work in XAML and have fine-grain control over the interface.

WPF/Silverlight also have excellent data binding capabilities, plus Silverlight can be run out of browser, so it might even be advantageous to skip WPF for the first version and do a Silverlight version. SL to WPF is much, much easier to port than WPF to SL (since SL is a subset of WPF).

For my project I am working on, it will be done only in SL4 because of the ability to run it out of browser as if it was a desktop app, eliminating the need to port it to WPF. Installing a Silverlight app onto a user's computer is simple, straightforward, and gives you an added benefit of using all your existing code and automatic updating.

like image 172
kamranicus Avatar answered Oct 13 '22 06:10

kamranicus