Take advantage of connection resiliency in EF Core to detect errors and retry commands and enable your ASP.NET Core application to overcome transient faults.

You can store encrypted values in your ASP.NET Core configuration file and seamlessly decrypt the values as you retrieve them. But there are, at least, two issues that you'll need to address.

Many of the Microsoft-provided ASP.NET parts like Membership and Personalization rely on the connectionStrings section in the config file.<BR><BR>The core problem I have with putting such things ...

Take advantage of the built-in support for OpenAPI in ASP.NET Core to automatically document your HTTP endpoints. Minimal APIs are supported too.