.NET 5 – One .NET to rule them all

There is No More .NET Core, it’s .NET 5

Here’s the umbrella of .NET 5 to the rescue. It’s a MAJOR change because of the following reasons:

As the first part of this unification scheme, Microsoft’s Xamarin mobile development platform will switch from using the Mono BCL to join other components leveraging the .NET Core BCL. With that move, Xamarin mobile development will be folded into .NET 5. That means that for the first time, one BCL-based framework will handle all app models:

ASP.NET Core
Entity Framework Core
Blazor
WinForms
WPF
Xamarin
ML.NET

Wait, WPF and WinForms made it into .NET 5? Yes, it’s true. Hello there, old friends! Nice to see them included in this runtime. The idea of using one SDK to build apps with is pretty exciting stuff, if you ask me.

Source: The Most Exciting Promise of .NET 5 | Okta Developer

Blazor’s Future: gRPC Is Key

Blazor guru Steve Sanderson detailed what Microsoft is thinking about the future of the revolutionary project that enables .NET-based web development using C# instead of JavaScript, explaining how gRPC is key, along with a new way of testing and a scheme for installable desktop apps.

Source: Blazor’s Future: gRPC Is Key — Visual Studio Magazine

Embracing nullable reference types | .NET Blog

Probably the most impactful feature of C# 8.0 is Nullable Reference Types (NRTs). It lets you make the flow of nulls explicit in your code, and warns you when you don’t act according to intent. The NRT feature holds you to a higher standard on how you deal with nulls,

Source: Embracing nullable reference types | .NET Blog

Proper List Support in C#

Implementing full list support over custom data structures in .NET

Source: Proper List Support in C# – CodeProject

.NET is Dead, Long Live .NET

.NET Core will become the successor to .NET, which will bring lots of upsides and few gotchas along the way as .NET Framework is shelved.

Source: .NET is Dead, Long Live .NET

Asynchronous Programming Models in C#

Pattern	Description	Based On	Notes
Thread based	By creating `System .Threading .Thread` instance	Managed Thread	Expensive, not recommended
Standard `BeginXxx` and `EndXxx` methods	By calling `BeginXxx` method with a user callback; calling `EndXxx` inside that user callback	Thread pool	Widely used, standard, recommended, support cancellation and continuation
ThreadPool	By calling `ThreadPool`’s static `QueueUserWorkItem` method	Thread pool	Widely used, recommended use as much as possible
Delegate	By calling Delegate’s `BeginInvoke` and `EndInvoke` instance methods	Thread pool	Less used
Event based	By subscribing to the appropriate event and calling the appropriate method	Thread pool	Avoid use as much as possible, not recommended
Task based	By creating `System .Threading .Tasks .Task` instance	A specified task scheduler	Recommended, supports all features of a thread pool pattern, and has many other features
`async` method and `await` expression	By using `async` and `await` keywords	Task based pattern	The new C# 5.0 asynchronous pattern

Nullable Reference Types in C# 8.0

Try out Nullable Reference Types With the release of .NET Core 3.0 Preview 7, C# 8.0 is considered “feature complete”. That means that the biggest feature of them all, Nullable Reference Types, is also locked down behavior-wise for the .NET Core release.

Source: Try out Nullable Reference Types | .NET Blog