.Net is receiving big changes from Microsoft this year. In May, the company made the announcement of merging .net core and .net framework into .net 5.0 soon.
.Net framework is used by developers for building web, windows, phone, Microsoft Azure, and Windows Server apps. .Net Core is a platform used for building cross-platform devices, IoT and cloud applications.
In September, Microsoft launched .net core 3.0 in which the .net products would be segregated. And, the latest move of the company is a little surprising that .net and .net core 3.0 will be merged into .net 5.0. This decision is made to benefit not just .net communities but the entire.net ecosystem.
Microsoft Company aforementioned that there’ll be simply single .Net accessible and developers are victimization it to focus on Windows, iOS, macOS, Android, watchOS, tvOS, WebAssembly, etc. While we won’t be seeing the update until late 2020, it is still a big step forward for the company.
There are four reasons to support this new release-
- .Net has a huge market share and is being used on billions of devices, but natively it runs only on the Windows platform. With the new release, it would be possible to run .net on other architectures also, including docker(natively).
- It would introduce critical optimizations to the entire .net environment, including Docker and Entity Framework.
- .Net core development experience is less decoupled from tools such as Visual Studio. It is better and that is why developers prefer using .net core.
- .net core includes modern development toolset and along with that the ability to run containers, deploy to the cloud and powerful command-line interface.
.Net Core and Mono
As the .Net core and Mono runtimes share many similarities, CoreCLR and Mono are going to act like drop-in replacements for every alternative. Asp.Net MVC developers are going to be ready to switch to pick out between the various choices of runtime.
It is stated that all .net 5 applications will leverage the CoreFX framework. Developers will be able to build .net 5 applications with the .Net CLI (command line), making sure that they have a common CLI tooling across projects.
.Net core 3.1 preview
Microsoft released the first preview of .Net core 3.1 in October that has key improvements in Windows Desktop and Blazor. .Net core 3.1 is expected to ship at the end of this year.
Improvements made in .Net core 3.1
The .Net core desktop runtime installer doesn’t install the .net core runtime for developers. .net core desktop runtime installer includes WPF and Windows forms, while .net core runtime has CoreFX and CoreCLR. Microsoft is changing this thing to make Desktop Runtime installer self-sufficient.
C++ and CLI was a promised part of .Net core 3.0 update. The company delivered it as a required dependency of WPF; however, a developer experience in visual studio and the software development kit was not there. Microsoft will be providing that experience with .Net core 3.1 and Visual Studio 16.4. Developers can get the support of C++ and CLI on Windows only.
The main aim behind .Net core 3.1 releases is to polish the features and scenarios offered by the company in .Net core 3.0. Microsoft has asked developers to install and test .Net core 3.1 previews 1 and provide them feedback. Currently, it is not yet supported or recommended for production purposes.
The new update is full of exciting features and developers are eagerly waiting to try them.
Have something to share related to this topic? Please let us know through your valuable comments below.