Clean Architecture with ASP.NET Core 3.0 

On the programming language popularity front (ranked by repository contributors), C# climbed a spot to No. 5, overtaking C++.  

• Improved support for .NET Core 3.1 

My last post investigated ways to build a .NET Core desktop/console app with a web-rendered UI without bringing in the full weight of Electron. This seems to have interested a lot of people, so I decided to upgrade it to newer technologies and add cross-platform support.

The result is a little NuGet package called WebWindow that you can add to any .NET Core console app. It can open a native OS window (Windows/Mac/Linux) containing web-based UI, without your app having to bundle either Node or Chromium. 

"End of Life" dates for .NET Core  

Installing Visual Studio 2019 16.4 will also install .NET Core 3.1 Preview 3, so you don’t need to separately install it. For Blazor development with .NET Core 3.1, Visual Studio 2019 16.4 is required. 

Go Live

This release is supported in production and you can call Microsoft support with issues. 

This is a technical deep-dive talk, and will explore possible design directions of .NET 5 and future releases. 

Here’s what’s new in this release for ASP.NET Core:

• New component tag helper
• Prevent default actions for events in Blazor apps
• Stop event propagation in Blazor apps
• Validation of nested models in Blazor forms
• Detailed errors during Blazor app development