JetBrains Unveils Plans for WinForms, WPF and More in Rider .NET IDE

JetBrains announced plans for Windows Forms, Windows Presentation Foundation (WPF), ASP.NET and more tooling in the next release of its popular Rider IDE for .NET development.

Microsoft itself presents JetBrains Rider as an IDE option on its list of .NET Tools & Editors, describing it thusly: "Cross-platform .NET IDE built using IntelliJ and ReSharper technology. It offers support for .NET and .NET Core applications on all platforms."

JetBrains goes into more detail: "Rider helps you develop .NET, ASP.NET, .NET Core, Xamarin, or Unity applications on Windows, Mac, or Linux. It provides rich editing support and code insight for languages used in .NET development, from C#, VB.NET, and F# to ASP.NET Razor syntax, JavaScript, TypeScript, XAML, XML, HTML, CSS, SCSS, JSON, and SQL."

The dev tooling specialist shared its plans for its next release cycle for Rider 2021.1 in a Jan. 25 roadmap post.

Some of the new features -- not all promised to be ready for the new release -- includes the following:

  • Improved welcome screen
  • Make the solution explorer load instantly without disrupting developers' workflow
  • A new localization infrastructure to support additional languages
  • ASP.NET scaffolding improvements
  • A WPF preview of reworked UI/UX with support for custom markups, design time attributes, templates, third-party controls, and resources from separate files and referenced assemblies
  • Better toolbox filtering and grouping for WinForms to make it feel more like Rider's other UIs
  • More refactorings and quick-fixes for F#
  • A debugger tweak: a quick toggle for breaking on unhandled exceptions (exception breakpoints) and stepping into external source code, which usually requires navigating through dialogs

Developers wanting to provide feedback such as feature requests can use the company's issue tracker. JetBrains didn't provide an expected release date for the next update.

About the Author

David Ramel is an editor and writer for Converge360.

comments powered by Disqus