Description
The following issue serves as an Epic, capturing task (issues) for individual work, such as but not limited to, conceptualizing and reasoning about various aspects of programming for .NET with numerous NuGet packages. Each package extends workload-agnostic cloud-native primitives, and fundamental building blocks for creating resilient, diagnostic-empowered, and robust features like health-checks and dependency injection (DI) auto-activation.
Each conceptual article with be interleaved into an appropriate section (or sub-section) of the existing .NET libraries content.
Important
The following two subsets, track currently published NuGet packages, publicly available in a prerelease state. If they're not listed here, then they're not going to have a conceptual article written for them:
.NET Extensions:
-
Microsoft.Extensions.Http.AutoClient -
Microsoft.Extensions.Resilience -
Microsoft.Extensions.Http.Resilience -
Microsoft.Extensions.Diagnostics.Probes -
Microsoft.Extensions.Diagnostics.ResourceMonitoring -
Microsoft.Extensions.Diagnostics.ExceptionSummarization -
Microsoft.Extensions.Diagnostics.HealthChecks.Common -
Microsoft.Extensions.Diagnostics.HealthChecks.ResourceUtilization -
Microsoft.Extensions.DependencyInjection.AutoActivation -
Microsoft.Extensions.AsyncState -
Microsoft.Extensions.AmbientMetadata.Application -
Microsoft.Extensions.TimeProvider.Testing -
Microsoft.Extensions.AuditReports
ASP.NET Core:
I'm going to tag @Rick-Anderson here, who from the ASP.NET Docs team can write a new conceptual article for the following NuGet package?