Microsoft announced today that .NET Core 3 Will support Windows desktop applications via a set of add-on packs. The firm expects to ship these releases in 2019.
“We are planning on releasing a first preview of .NET Core 3 later this year and the final version in 2019,” a post to Microsoft’s .NET Blog notes. “The highlight of .NET Core 3 is support for Windows desktop applications, specifically Windows Forms, Windows Presentation Framework (WPF), and UWP XAML.”
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
If you’re familiar with .NET Core, you know that this platform was designed to create an open and cross-platform version of the .NET Framework, which was Windows-only. The addition of Windows desktop application support doesn’t change this mission. But it does expand the scope of .NET Core to include key workloads that today still require the deprecated .NET Framework.
“Support for Windows desktop will be added as a set of ‘Windows Desktop Packs’, which will only work on Windows,” the software giant notes. “.NET Core isn’t changing architecturally with this new version. We’ll continue to offer a great cross-platform product, focused on the cloud.”
Today, .NET Core for the desktop will offer performance improvements, easy testing of new .NET Core versions, machine-global and application-local deployment support, and support for the .NET Core CLI tools and SDK-style projects in Visual Studio. But with version 3, the feature-set is improving dramatically, with access to the full Windows 10 (WinRT) API set, the ability to host UWP XAML controls in WPF and Windows Forms applications, and the ability to host UWP browser and media controls.
“Today’s news demonstrates a large investment and commitment in Windows desktop applications,” Microsoft claims.
skane2600
<p>So basically with extra steps you can do with .NET Core 3 what you can already do "out of the box" with .NET "regular" (as long as you're not in S mode, in which case you can't use desktop programs with either version).</p>
skane2600
<blockquote><a href="#272494"><em>In reply to unkinected:</em></a></blockquote><p>Usually these "resets" are at least embracing a new approach or adding significant new capabilities. I don't see how adding desktop features to .NET Core adds anything new.</p>
skane2600
<blockquote><a href="#272663"><em>In reply to mahoekst:</em></a></blockquote><p>You aren't limited to using only a single .NET version on a computer.</p>
skane2600
<blockquote><a href="#272582"><em>In reply to RM:</em></a></blockquote><p>But this newest change applies only to Windows, so it doesn't have anything to do with supporting multiple OS's. In a way it's kind of an odd development for a what was supposed to be a cross-platform technology. </p><p><br></p><p>I guess if they drop development and support for .NET "normal" it's good that there's a replacement that is backwards compatible, but the same could have been achieved by just staying the course at a much cheaper cost.</p>