The time is nearly upon us, bigger than Jesus’ Second Coming and 100 times more exciting than his birthday (for tech nerds anyway). It is of course (drum roll please) … Microsoft’s Preview 9 unveiling of its brand spanking new .NET CORE 3.0 SDK!
On the 5th of September 2019, Microsoft released their latest preview of the new .NET Core, giving us a further glimpse into 3.0’s latest features, performance improvements and capabilities. The five-thousand-word document goes into headache inducing detail about the 3.0 update.
But, for the vast majority of people out there who don’t have a spare 4 days to digest the entire document, we’re going to focus on the biggest changes that will be brought about by the new update.
1. .NET Platform – Dependent Intrinsics
According to Microsoft, the new 3.0 version will support API’s that will allow Window’s systems to access perf-orientated CPU instructions such as SIMD sets or Bit Manipulation Instructions. Now, for those reading this thinking what the hell has just happened, this basically means any data processing that occurs within the .NET library will experience significant performance improvements. By just how much exactly is still to be confirmed by Microsoft, but the beta testing appears to be showing some pretty good results.
2. Default Executables
Framework-dependent executables will now be built by default within .NET Core 3.0, which means less time having to create and deploy separate FDE’s outside of the .NET Core. Earlier .NET versions only allowed FDE’s to be deployed within the Core if the app you were targeting was installed in the host system. This will likely save developers a significant amount of time deploying their apps as FDE’s.
3. Assembly Linking
The .NET 3.0 SDK has a tool that can reduce the size of apps by identifying unused assemblies and trimming them through analysing IL. Previously, self-contained apps transferred unnecessarily large amounts of code from their libraries when transferred from hosting systems to .NET. This tool detects what code is and isn’t required and trims the unnecessary code out. According to Microsoft, this significantly reduces the deployment size of apps.
4. Tiered Compilation
Tiered Compilation is now a default setting on .NET Core 3.0 that will automatically enable the runtime to use the Just in Time compiler more adaptively to every app. Instead of tarring every app with the same brush, the 3.0 Tiering feature will assign unique runtimes to every app which should help their performance throughout the entire development and deployment process.
So there we have it (more or less), the biggest highlights of Microsoft’s new .NET Core 3.0. Rumours suggest that the new version will be rolled out fully some point next week. The question still remains, will 3.0 improve the lives of developers, data scientists, BI analysts and confused content writers across the world, or will it be just another over-hyped system update? For now, only time will tell.
At the Bridge we specialise in providing .NET developer roles to professionals across the UK, click here to view jobs suited to you. To keep up to date with the latest tech news, follow us on Twitter @BridgeITRec