The .NET Core SDK 3.1.106 includes .NET Core 3.1 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 3.1.106, the following command will show that you're running version 3.1.106 of the tools. 

A simple yet organized project template for building ASP.NET Core APIs in .NET Core 3.1

Tools and Frameworks Used

• .NET Core 3.1
• ASP.NET Core - For building RESTful APIs
• Dapper - For data access.
• AutoMapper - For mapping entity models to DTOs.
• AutoWrapper - For handling request Exceptions and consistent HTTP response format.
• AutoWrapper.Server - For unwrapping the Result attribute from AutoWrapper's ApiResponse output.
• Swashbuckle.AspNetCore - For securing API documentation.
• FluentValidation.AspNetCore - For Model validations
• Serilog.AspNetCore - For logging capabilities
• IdentityServer4.AccessTokenValidation - For JWT Authentication handling
• Microsoft.Extensions.Http.Polly - For handling HttpClient Resilience and Transient fault-handling
• AspNetCoreRateLimit - For controlling the rate of requests that clients can make to an external API based on IP address or client ID.
• AspNetCore.Diagnostics.HealthChecks - For performing health checks
• Microsoft.AspNetCore.Diagnostics.HealthChecks - For getting the results of Health Checks in the application
• AspNetCore.HealthChecks.UI - For Health Status visualization
• xUnit and Moq - For unit testing.  

FluentValidation 9.0 is a major release that included several breaking changes. Please review this document before upgrading from FluentValidation 8.x to 9. 

The following article describes how to developing APIs using Actor model in ASP.NET Core. It will show some benefits of build APIs using actor model pattern and some good reasons about adopting Orleans.NET as actor model framework

In case you are curious, a new benchmark appeared. The benchmark is really simple at present, but I think their plans are to increase the complexity over time to show a more real-world use case than something like the TechEmpower benchmarks which are typically optimized for performance.

.NET 5 Preview 6 is now available and is ready for evaluation. Here’s what’s new in this release:

• Blazor WebAssembly template now included
• JSON extension methods for HttpRequest and HttpResponse
• Extension method to allow anonymous access to an endpoint
• Custom handling of authorization failures
• SignalR Hub filters 

OK – it’s finally done. I published v4 to Nuget earlier today. You can find the complete set of changes/bug fixes/breaking changes here. 

In this article, we will build and learn how to send emails with ASP.NET Core in Just 5 Simple Steps. Our application will send emails in plain text, support attachments (multiple attachments at once) and also we will learn how to Send Branded Emails using HTML Templates. 

What’s new?
Reloadable endpoints via configuration for Kestrel

Kestrel now has the ability to observe changes to configuration passed to KestrelServerOptions.Configure and unbind from existing endpoints and bind to new endpoints without requiring you to restart your application. 

In this tutorial you will learn how to create a .NET Core gRPC client and an ASP.NET Core gRPC Server that will communicate with one another