Asynchronous Main (it is going to be released in version 7.1)
Default Literal (it is going to be released in version 7.1)
Readonly ref (it is going to be released in version 7.2)
Default interface methods (it is going to be released in version 8.0)
Optional tuple names (to be released in 7.1)
 

This post will be comparing the performance of RyuJIT in .NET Framework 4.6.2 to its performance in .NET Core 2.0 and .NET Framework 4.7.1.  

Here’s what’s new in this preview release:

• Smaller SignalR, Blazor Server, and MessagePack scripts
• Enable Redis profiling sessions
• HTTP/3 endpoint TLS configuration
• Initial .NET Hot Reload support
• Razor compiler no longer produces a separate Views assembly
• Shadow-copying in IIS
• Vcpkg port for SignalR C++ client
• Reduced memory footprint for idle TLS connections
• Remove slabs from the SlabMemoryPool
• BlazorWebView controls for WPF & Windows Forms 

Open source MVVM framework for ASP.NET Core and OWIN 

View

@viewModel DotvvmDemo.CalculatorViewModel, Dotvvm
    
<p>
    Enter the first number: 
    <dot:TextBox Text="{value: Number1}" />
</p>
<p>
    Enter the second number: 
    <dot:TextBox Text="{value: Number2}" />
</p>
<p>
    <dot:Button Text="Calculate" Click="{command: Calculate()}" />
</p>
<p>
    The result is: {{value: Result}}
</p>

ViewModel

using System;
    
namespace DotvvmDemo 
{
    public class CalculatorViewModel 
    {
            
        public int Number1 { get; set; }
            
        public int Number2 { get; set; }
            
        public int Result { get; set; }
            
        public void Calculate() 
        {
            Result = Number1 + Number2;
        }
    }
}

AutoMapper has been a popular library in the .NET open source community for a long time. As their site says:

AutoMapper is a simple little library built to solve a deceptively complex problem - getting rid of code that mapped one object to another. This type of code is rather dreary and boring to write, so why not invent a tool to do it for us? 

To update a document in MongoDB, I used to fetch it, update the values, and save back the entry. I would question the need for an update method. Looking back, it's evident that performance optimizations were hardly a concern when working on a personal project.

Here’s a summary of what’s new in this preview release:

• Support for route handler filters in minimal APIs
• Improved unit testability for minimal route handlers
• Bind using TryParse in MVC and API controllers
• New Results.Stream() overloads
• Improved HTTP/2 performance when using many streams on a connection
• New ServerReady event for measuring startup time
• Developer exception page dark mode 

Today, we’re releasing .NET 5.0 Preview 2. It contains a set of smaller features and performance improvements. We’re continuing to work on the bigger features that will define the 5.0 release, some of which are starting to show up as initial designs at dotnet/designs.  

In this video, I show ten extremely useful Visual Studio features: - Enhanced Clipboard - Run To Cursor Debugging - Tracking Active Solution Explorer Item - Fast File Navigation - Tabs - Previewing and Pinning - Code Cleanup Configuration - Vertical Selection - Better Git Pull - Improved Performance On Load - Special Pasting