.NET 6 Preview 5 highlights SDK workloads, the foundation of .NET unification – Visual Studio Magazine



.NET 6 Preview 5 Highlights SDK Workloads, the Foundation of .NET Unification

“The future is definitely here,” said Richard Lander of Microsoft announcing the new .NET 6 Preview 5.

November’s .NET 6 GA release will culminate Microsoft’s .NET unification effort, bringing together all of the disparate desktop, web, mobile, cloud, and device tools under one platform.

This includes Xamarin mobile technology and newer tools like WebAssembly, which drives the client-side Blazor effort that enables web development in C # instead of JavaScript.

The broad outlines of what to expect .NET are detailed in the .NET Themes site.

.NET Themes
[Click on image for larger view.] .NET Themes (source: Microsoft).

Key to the unification effort is a new schema for SDK workloads, allowing Microsoft to add support for new types of applications without increasing the size of the SDK.

This is one of the highlights of the new .NET 6 Preview 5, announced on June 17 in a blog post by Lander, program manager for Microsoft’s .NET team.

“We are now in the second half of the .NET 6 release and starting to see some important functionality coming together,” he said. “A great example is .NET SDK Workloads, which is the foundation of our vision to unify .NET and supports more types of applications. Like other features, it combines to deliver a compelling end-to-end user experience. ”

.NET 5
[Click on image for larger view.] .NET 5 (source: Microsoft).

He explained in more detail the functionality on GitHub in the context of .NET 5, which was originally supposed to merge the unification effort, which had to be postponed for a year due to the COVID pandemic. 19 and other issues.

The .NET calendar
[Click on image for larger view.] The .NET calendar (source: Microsoft).

The SDK workload scheme will replace the old monolithic approach to the SDK, which was cluttered with long build times and large distribution sizes.

“Instead, all new workloads will be created and delivered separately from the SDK and can be obtained through your preferred installation tool (like Visual Studio Installer, a Linux package manager, or the .NET CLI),” a Lander said. “Ultimately, we intend that all .NET workloads will follow this model, resulting in a very small and focused SDK.

It therefore essentially acts as a package manager for the .NET SDK.

Last month, .NET 6 Preview 4 introduced the ability to install optional SDK workloads through the Command Line Interface (CLI). For this preview, the .NET MAUI and Blazor AoT workloads were supported, which can be retrofitted to the .NET SDK for various scenarios.

In .NET 6 Preview 5, the Workloads feature gets list and update verbs.

“These new capabilities give a sense of the expected end-to-end experience,” Lander said. “You will be able to quickly establish your preferred environment with a few simple commands and keep it updated over time.”

  • dotnet workload list will tell you what workloads you have installed.
  • dotnet workload update will update all installed workloads to the latest available version

Plans for functionality in NET 6.0+ include:

  • Expose the full set of .NET CLI verbs for acquisition
  • Separate / expose WPF, Windows Forms, and ASP.NET Core as workloads
  • Enable acquisition of all workloads through the .NET CLI and at least the ASP.NET Core and Web Assembly workloads available through Linux package managers
    • Define and implement the interaction with the installation tools.

Here are some other highlights of .NET 6 Preview 4:

  • Validating the NuGet package

  • More Roslyn analyzers

  • Enable Custom Guards for Platform Compatibility Analyzer

  • The ability to define a default font for Windows Forms

    Examples of default fonts
    [Click on image for larger view.] Examples of default fonts (source: Microsoft).
  • Improvements to Microsoft.Extensions applications

  • JsonSerializer source generation
  • WebSocket data compression

  • Sock proxy support

  • Support for OpenTelemetry metrics
  • BigInteger performance improvement

    BigInteger performance increase
    [Click on image for larger view.] BigInteger performance increase (source: Microsoft).
  • Support for OpenSSL 3
  • Support for Objective-C interoperability

“.NET 6 Preview 5 is perhaps the biggest preview to date in terms of breadth and amount of functionality,” Lander said in conclusion. “You can see how the functionality of Roslyn affects the functionality of low-level libraries, with generators and source analyzers. The future has really arrived. We now have a very capable compilation toolchain that allows us to produce highly optimized and correct code, and allows the exact same experience for your own projects. ”

About the Author

David Ramel is editor and writer for Converge360.


About Author

Leave A Reply