The document summarizes updates to .NET technologies. Key points include:
- .NET 5 will unite .NET Core and .NET Framework, with all new features going exclusively to .NET 5. The Framework will remain at version 4.8.
- Benefits of .NET 5 include smaller app sizes, performance improvements, and better project files.
- New features are coming to Windows Forms, WPF, C#, XAML tooling including hot reload and design time data.
- ClickOnce deployment is now supported for .NET Core and .NET 5 apps. WinUI 3 provides a modern XAML framework decoupled from Windows 10.
3. Big Picture
Highly-compatible,
targeted improvements,
like last few releases
• .NET Framework support unchanged
(supported for life of Windows)
• Side-by-side support
• Self-contained EXEs
UWP
Windows-only
DATAWEB
ASP.NET
Core
EF 6
EF Core
AI/ML
ML.NET
WPF
.NET Core 3.NET Framework 4.8
.NET STANDARD
Existing App
Highly
compatible
updates
Install .NET Core
updates per your
needs
Modernize Desktop Apps with .NET Core 3
Windows-only Cross-platform
Windows
Forms
Update .NET Framework Apps
• XAML Islands - WinForms & WPF apps can host UWP controls
• Full access to Windows 10 APIs
FEATURES IN BOTH FXs
5. • .NET 5 will be the future of .NET
• all new improvements, .NET APIs, runtime capabilities, and language features will go
exclusively to .NET 5
• .NET Framework will remain where it is at the highest version of 4.8 and receive only
Windows essential (Windows and security) updates
• Allows “side-by-side” deployment of multiple versions of .NET 5 on the same compute
• Smaller applications sizes with Assembly Trimming feature
• Single-file executables
• Significant BCL performance improvements
• More choice on runtime experiences
• Better project files (SDK-style .csproj)
• New features in Windows Forms, WPF, C#, etc.
• Stable release schedule
Benefits of .NET 5
6. • Windows Form | aka WinForms
• Windows Presentation Fondation | aka WPF
• Universal Windows Platform | aka UWP
• Windows UI | aka WinUI
Desktop Technologies
7. • .NET Core: change the target FW* !
• .NET FW: Try Convert is a global tool that attempts to upgrade your project file
from the old style to the new SDK style and retargets applicable projects to .NET
5.
* https://docs.microsoft.com/en-us/dotnet/core/compatibility/3.0-3.1-windows-forms
https://docs.microsoft.com/en-us/dotnet/core/compatibility/3.1-5.0#windows-forms
Porting from .NET Core / Framework
8. • Improvement to in-app toolbar
• Inline color previews
• Design Time Data
https://docs.microsoft.com/visualstudio/xaml-tools/xaml-designtime-data
• Refresh designer button
• Suggested Actions
• Hot Reload
• XAML Binding Failures
• New Designer for .NET FW apps
New features in XAML Tooling
9. • VS 2019 16.7
• XAML Designer: Design-Time data using «d:»
• VS 2019 16.8
• XAML Data Binding Diagnostic Experiences
• XAML Hot Reload – WPF & UWP Improvements
• VS 2019 16.9
• XAML Hot Reload – Xamarin.Forms & WinUI 3.0
New features in XAML Tooling
10. • Task Dialog
• Updates to ListViewGroup, FileDialog, TrackBar, etc.
• Over 150 PRs from OSS community
• Memory and performance optimizations, accesibility
improvmnets, etc.
• Designer
• Support for most controls
• Support for third-party control vendors
• Data scenario are coming
WinForms – New Features
11. • ClickOnce is back for .NET Core & .NET 5 developer starting with
VS 2019 16.8 and Mage CLI tool
• Publish from VS 2019 version 1.8 or use the newly open-source
«dotnet-mag» CLI tool
• Supports .NET Core 3.1 and .NET 5 project for WPF, Windows
Forms and Console apps
• New Launcher, a manage entry-point for ClickOnce
ClickOnce in .NET 5
12. • .NET 5 includes support for WinUI 3 - the
evolution of UWP's XAML technology.
• It includes the entire presentation layer
(XAML, composition, and input) decoupled
from the Windows 10 OS, an extensive
controls library (including WebView2), and
allows you to use the desktop application
model in addition to the UWP app model.
• WinUI 3 is still in development, but you can
use the Preview version that's already
available. Visit https://aka.ms/winui3
New .NET desktop: WinUI 3