With .NET 5, Microsoft would like to produce a single .NET run-time environment and a usable infrastructure everywhere.



[ad_1]

Today, we announced that the next release, after .NET 3.0, will be the .NET version and will be the next major release of the .NET family. There will only be one .NET future and you can use it to target Windows, Linux, MacOS, iOS, Android, tvOS, watchOS and WebAssembly etc.

Microsoft claims to have added approximately 50,000 .NET Framework APIs since the launch of the .NET Core project.

It should be noted that .NET Core does not support ASP.NET WebForms, Windows Forms, and Windows Presentation Foundation (WPF). This means that .NET Core is available without support for a User Interface Framework to the dismay of many developers. However, Microsoft has promised to bring a solution by making support for the development of Windows Desktop applications in .NET Core 3.0 their top priority.

So when introducing .NET Core 3.0, the editor described three important scenarios for the developer community that will be made with this release:

  • Side-by-side versions of .NET that support Winforms and WPF: Before launching this release, Microsoft explained that there could only be one version of the .NET Framework on one machine. This means that with the installation of a .NET Framework update via Patch Tuesday or Windows updates, there is a risk that a security patch, a bug fix, or a new API may interrupt the application's operations on the machine. . With .NET Core, Microsoft intends to solve this problem by allowing multiple versions of .NET Core to coexist on the same machine. Applications can lock a specific version and pass another version after testing.
  • Integrate .NET directly into an application: Because only a version of the .NET Framework could be installed on a machine, it was imperative to install the latest version to take advantage of a new framework or language feature. With .NET Core, you can deliver the framework with your application. This allows you to take advantage of the latest version, features, and APIs without having to wait for the framework to be installed.
  • Take advantage of the .NET Core features: .NET Core is a floating, open source version of .NET. Now, WinForms and WPF applications in Windows can take advantage of the latest .NET Core features, which also include more essential fixes for better support for high-resolution display.

.NET Core 3.0 reduces the capacity gap with the .NET Framework 4.8 by enabling Windows Forms, WPF, and Entity Framework 6. This development builds on this work. The .NET kernel and the best of Mono allow you to create a single platform that you can use for all your modern .NET code.

We plan to release .NET 5 in November 2020, and the first prversion will be available in the first half of 2020. It will be supported with future upgrades of Visual Studio 2019, Visual Studio for Mac and Visual Studio Code.

.NET 5 = Next version of .NET Core

.NET 5 is the next step in .NET Core. The project aims to improve .NET in several ways:

  • Create a single .NET Framework and Execution Environment that can be used anywhere, providing consistent execution behaviors and developer experiences.
  • Develop .NET features by leveraging the best of .NET Core, .NET Framework, Xamarin, and Mono.
  • Build this product from a single code base on which developers (Microsoft and the community) can work and grow together, enhancing all scenarios.

This new project and new direction is a watershed for .NET. With .NET 5, your code and project files will look the same regardless of the type of application you are designing. You will have access to the same runtime, API, and language features for each application. This includes new performance improvements in corefx, virtually every day.

Everything you love in .NET Core will continue to exist:

  • Open source and GitHub-oriented community.
  • Multiplatform implementation.
  • Supports platform-specific feature operation, such as Windows Forms and WPF on Windows, as well as native links to each native Xamarin platform.
  • High performance.
  • On the installation side.
  • Small project files (SDK style).
  • Command line interface (CLI).
  • Integration of Visual Studio, Visual Studio for Mac and Visual Studio Code.

Here's what will be new:

  • You'll have more options in running experiments.
  • Java interoperability will be available on all platforms.
  • Objective-C and Swift interoperability will be supported across multiple operating systems.
  • CoreFX will be keen to support static .NET compilation (AOT), smaller footprints, and support for more operating systems.

Script

Microsoft plans to deliver .NET Core 3.0 in September, .NET 5 in November 2020, and then plans to release a core version of .NET once a year every November:

We have omitted version 4 because this naming can disrupt familiar users with the .NET Framework, which has been using the 4.x series for a long time. In addition, we clearly wanted to communicate that .NET 5 was the future of the .NET platform.

We also took the opportunity to simplify the names. We thought that if there was only one .NET future, we would not need a clarifying term like Core. The abbreviated name is a simplification and also indicates that .NET 5 has uniform functionality and behavior. Do not hesitate to continue using the .NET Core name if you prefer.

Experiment Execution

Mono is the original cross-platform implementation of .NET. It was the source of an open source .NET Framework alternative that then went on to target mobile devices as the popularity of iOS and Android devices grew. Mono is the runtime used as part of the Xamarin.

CoreCLR is the runtime used as part of .NET Core. It was primarily designed to support cloud applications, including the largest Microsoft services, and is also used for Windows desktop applications, IoT, and machine learning.

Together, .NET and Mono runtime environments have many similarities (both of which are .NET runtime environments), but also unique and valuable features. It makes sense to let you choose the desired execution experience. That's why Microsoft is creating direct replacements for CoreCLR and Mono. The publisher plans to simplify things as a build option to choose from different deployment options.

Source: Microsoft

See too:

JetBrains announces the availability of 2019.1 ReSharper Ultimate, its suite of tools for .NET and C ++ developers
.NET Core 3.0 Preview 4 is available and comes with a build built into the MJ control and WinForms Chart
Microsoft announces ML.NET 1.0 RC, the latest visualization version of its machine learning framework, with support for TensorFlow templates
ASP.NET Core is the third fastest web server, responding to 7 million HTTP / s requests, according to a TechEmpower test

[ad_2]

Source link