I think JetBrains made a mistake by not including a Windows Forms designer much sooner, that supports 3rd-party controls/components [0] in the Rider IDE. Dealbreaker for me now and for many other companies I've worked for or know of. Unfortunately, we had to choose Visual Studio because of this.

According to their own developer survey, Windows Forms was at 22% in 2023 [1].

WinForms != legacy, because it's very extensible! Microsoft still maintains it (last update was 1 month ago). It is also still one of the flagship products for companies that make 3rd-party controls like DevExpress [2], Telerik, Infragistics, GrapeCity and several others.

Students in academia today will not learn about WPF, WinUI, UWP and whatever else MS' pushing. They learn Windows Forms - in my country and in Europe at least.

Hopefully we'll get to switch over to Rider soon, but it's been 5 years already [3]. Big mistake.

[0] https://www.jetbrains.com/help/rider/Working_with_Windows_Fo... ("Unfortunately the support of custom controls is not implemented yet (as of v.2023.3)")

[1] https://www.jetbrains.com/lp/devecosystem-2023/csharp/

[2] https://www.devexpress.com/products/net/controls/winforms/

[3] https://youtrack.jetbrains.com/issue/RIDER-25764