Filthy Microsoft opens its .NET Core 3 trench coat for the sixth time

www.theregister.co.uk | 6/13/2019 | Staff
Coraav (Posted by) Level 3
Click For Photo: https://regmedia.co.uk/2019/06/13/trenchcoatflasher.jpg

Microsoft has continued its quickfire pace of .NET Core 3 updates, flinging preview 6 at developers keen on the open-source platform.

Program manager Richard Lander also took time to report on the company's progress in shovelling the source behind the venerable Windows Presentation Framework (WPF) into GitHub. It's safe to say that the work has involved a tad more than removing all the swears.

NET - Front - Framework - Event - Pipe

On the .NET Core 3 front, the framework now supports multiple Event Pipe sessions, allowing scenarios such as consuming events with EventListener in-proc and simultaneously having out-of-process event pipe clients.

Unsurprisingly, the gang has added a number of Perf Counters to keep track of things, including values for ThreadPool Work Items and Lock Contention rate.

Lander - ReadyToRun - R2R - Format - Time

Lander also highlighted the ReadyToRun (R2R) format, aimed at speeding the startup time of a .NET Core app by cutting back on what the Just In Time (JIT) interpreter has to do while the app is firing up.

Yes – we're talking about another take on Ahead Of Time (AOT) compilation.

JIT - Things - Downside - Bloating - Intermediate

Since there is less for JIT to do, things are snappier to load. However, the downside is a bloating of the binary since the old Intermediate Language (IL) code is still needed as well as the native version.

AOT has been around for a while. .NET developers doubtless remember the joy of NGEN, which insisted on compiling on...
(Excerpt) Read more at: www.theregister.co.uk
Wake Up To Breaking News!
Sign In or Register to comment.

Welcome to Long Room!

Where The World Finds Its News!