Microsoft .NET Core Version 2.1, a cross-platform implementation of the company’s .Net development platform, has been released, featuring improvements to build time performance and tools deployment. Version 2.0 will reach end-of-life status on September 1, 2018, and patches will no longer be provided for it.
And Microsoft expects to ship .Net Core 3 in 2019, with the first beta expected later in 2018.
And Microsoft expects to ship .Net Core 3 in 2019, with the first beta expected later in 2018.
Features of .NET Core
Yes, as it is the new generation .NET framework, it contains all features of .NET framework + its own new features, let’s go through them
- Cross platform support : .NET Core is supporting development of apps that can be deployed beyond windows platform, we can deploy our apps on Linux or on MacOS.
- Containers and Dockers support : Containers and dockers are very famous in these days, they can be easily adaptable by cloud technologies, Don’t worry .NET Core has full support of these components.
- Performance Improvement.
- MVC and web API merged : Before .NET Core, Developer needs to use MVC and Web API separately to create REST services using JSON, but .NET Core does job more simpler and merged them in a single module.
- Seamless support to Microservices.
- Command line development possible on Windows, MacOS, Linux.
- It support adjacent .NET versions per applications.
Now let’s discuss the road ahead for .NET Core 2.1:-
Build-Time Performance: For the developers into .NET Application Development this will be bring good news as build-time performance has been improved in .NET Core 2.1 especially for incremental build. These improvements valid for both .NET build on the command line and to builds in Visual Studio. Microsoft has also made improvements in the CLI tools and in the MSBuild in order to make the tools deliver much faster experience to the developers.
.NET Core Global Tools: In .NET Core 2.1, it will include a new deployment and extensibility mechanism for tools. This new experience is similar to Node global tools. Microsoft has used the same syntax and experience. .NET Core tools are .NET Core console apps which are packaged and acquired as NuGet packages. These tools are framework dependent application by default and include all of the NuGet dependencies. This implies that a given global tool will run on any OS or chip architecture by default. Microsoft expects a whole new ecosystem of tools to establish itself for .NET. Some of these tools will be specific to .NET Core development and many of them will be general in nature.
HttpClient Performance: Outgoing network requests are important part of application performance for microservices and other types of application. .NET Core 2.1 has a new HttpClient handler which is rewritten for high performance. Microsoft is also including a IHtt[ClientFactory fearture that provides circuit breaker and other services for HttpClient calls. This new feature has been built on top of the new HttpClient handler.
Windows Compatibility Pack: When you port existing code from the .NET framework to .NET Core, you can use the new Windows compatibility pack. It provides access to an additional 20,000 APIs more than what is available in .NET Core. This includes System.Drawing, EventLog, Performance Counters, Windows Services an EventLog.
Summary
We have discussed some of the new features which are being added into .Net Core 2.1 by Microsoft. Till now the feedback and experience of the developers has been great. These improvements will make the .NET Core development even more easier and make the applications run more faster while using less memory.
