or subscribe with
Join 19,300+ readers for one email each week.
Digests » 219
How would you like to learn about the hottest topics, straight from the experts? At the O'Reilly Velocity Conference (Sep 30-Oct 3 in New York), you'll learn about SRE from Google, Kubernetes from Microsoft, the advantages or disadvantages of running containers at production from Github, and much more. The Velocity program helps you get the training you need to stay ahead of the trends that impact your professional development, including systems performance, scalability, cloud-based infrastructure, security, and leadership. As a C# Digest reader, Velocity is giving you 20% off Gold, Silver, and Bronze passes! Grab your pass before Early Price ends on August 17 to save up to $599. Just use code CDIG20 at checkout.
this week's favorite
Tiered compilation is a significant new performance feature that we are making available as a preview for anyone to try out, starting in .NET Core 2.1. In many scenarios that we have tested, applications start faster and run faster at steady state.
As we are already familiar with the basics of memory and data structures used by .NET applications, in this third post from .NET Internals series we’re going to dig into boxing and unboxing and their performance implications.
Over the last couple of decades, the amount of boilerplate code necessary to develop Windows applications has increased dramatically; which takes away from .NET’s early roots as a RAD or Rapid Application Development framework. Microsoft’s attempt to counter-act this is the Windows Template Studio for UWP applications.
At Build 2018 we announced that we are enabling Windows desktop applications (Windows Forms and Windows Presentation Framework (WPF)) with .NET Core 3.0. You will be able to run new and existing Windows desktop applications on .NET Core and enjoy all the benefits that .NET Core has to offer, such as application-local deployment and improved performance.
Since Microsoft anounced .NET Core, there hasn’t been a clear vision vision on what cross-platform GUI development would look like. Although they plan to support WPF in .NET Core 3.0, it will still only target Windows.