.NET Core 2.1 has been out for a few months now. It has brought of hype with its release as slated to offer tons of new features for the developers across the world. The journey started in 2002 when Microsoft started to work on a standard. Sooner or later, new challenges arrived and .NET Core was officially made an open source for the greater good challenging the likes of Java and other similar solutions in the market.

In today’s article, we will be going through the review of .NET Core 2.1. If you didn’t get the chance to use it or need reviews before putting your hands on it, then this review is for you. Let’s get started.

.NET Core 2.1

.NET Core 2.1 just like previous .NET Core meets the .NET standard. This means that you will get the basic APIs that each .NET implementation comes with.

Faster Builds

Developers always want to improve their time to delivery. However, building a solution can eat a lot of time. It is now easy to write software, but developers are now stuck on how much time it takes to build their solution. Microsoft understands that and has significantly improved the build times while building code. Overall, .NET core 2.1 will help faster build times using automation build tools, especially when working with large projects.

Socket Performance

Apart from the build time improvement, the socket performance has also increased. This means that servers can now communicate with the apps faster, improving connectivity between computers across a network. The improved socket performance is done due to the introduction of a new managed class which is written in C#. Earlier, the code is written in native C which introduced some latency. The class that we are talking about here is the SocketHttpHandler class. By going through a non-native approach, response time between computers is decreased significantly. Also, it ensures consistent app behavior across systems and platforms.

Improved Security

Security has always been a concern for developers and with .NET Core 2.1 we see new classes and other improvements. These security features are added to ensure that it meets the .NET standard.

The new class addition includes the CryptographicOperations Class . It offers two features that can change how developers secure their application. It includes ZeroMemory and FixedTimeEquals.

ZeroMemory protects the in-memory from leaking sensitive secrets. It is an in-memory clearing routine.

FixedTimeEquals, on the other hand, enables developers to protect their application against the side-channel attack that generally happens on the long screens. It removes the ability of the hacker to guess password/username through brute force method. It protects the system by not enabling attackers to understand the time taken to verify the username-password combination. It should be noted that hackers can use the time required to verify information to guess how close they are to crack it.

Apart from the CryptographicOperations Class, other security functions are also added including the elliptic-curve Diffie-Hellman(ECDH). It is a good public-key cryptographic algorithm that developers can use to have improved performance.

Self-Contained Applications

With .NET Core 2.1, you will now have the option to release self-contained applications. It gives you the ability to publish whole packages that contains all the runtime and .NET Core libraries to run the application without affecting other applications. This provides the developer with a lot of flexibility as they can now run two applications with different .NET Core version parallelly.

Global Tools

The inclusion of global tools is a welcome change. This will enable developers to run commands on a global scale rather than commands that run only within a specified folder where you created it. These tools can be published as NuGet packages. Once done, you can use the command line to run them:

install-g <<Tool Name>>



The new .NET Core 2.1 is promising and offers new features that can change and impact developers workflow. If you are interested in trying it, we recommend download the SDK and runtime and try it yourself.
This leads us to the end of the .NET Core 2.1. We hope that you found the review useful. If you did, don’t forget to comment below and let us know why you liked it.

About the Author

Mahendra is associated with Asentech as a technical lead for over five years. He is an expert in .Net, Sitecore, AngularJS, JavaScript. He has played a pivotal role in providing high end solutions to various clients at Asentech.