-
Notifications
You must be signed in to change notification settings - Fork 6k
Add conceptual documentation for new .NET Extensions packages #49372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @copilot - This looks good so far, but I'm seeing the IAsyncState<T>
doesn't exist. Instead it's simply IAsyncState
, please see my ssuggestions.
@copilot please address my feedback |
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Fixed in commit 4c82751. Updated all references from |
Summary
Created comprehensive conceptual documentation for 5 new .NET Extensions packages totaling 1,544 lines of documentation with 40+ complete code examples.
Articles Created
All articles follow Microsoft documentation standards including:
Recent Updates
IAsyncState
references in async-state.md to use non-generic interface instead ofIAsyncState<T>
Original prompt
This section details on the original issue you should resolve
<issue_title>[Epic] Docs for new .NET Extensions</issue_title>
<issue_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.
.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?
Microsoft.AspNetCore.HeaderParsing
</issue_description><agent_instructions>Please continue work on this issue, the task list has links to NuGet packages that need to have corresponding conceptual content. Please start creating new articles next to the existing ones under .NET Fundamentals / Extensions. These packages are a result of the: https://github.com/dotnet/extensions repo. Use that as a source of truth.</agent_instructions>
Comments on the Issue (you are @copilot in this section)
Fixes #37411
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Internal previews