Show Kestrel overview feature list for .NET 8+ and move memory management to dedicated article

[Copilot]

Fixes #36376

Description

The Kestrel overview page previously showed enhanced feature listing only for .NET 10. This PR extends that feature list to .NET 8 and later, while moving memory pool content to a dedicated article as requested by the maintainer.

Changes

• New article: Created memory-management.md under Kestrel section (moniker: >= aspnetcore-10.0)

  • Covers automatic memory pool eviction (new in .NET 10)
  • Documents IMemoryPoolFactory usage and custom implementations
  • No include file references (clean standalone article)

• Kestrel overview (kestrel.md): Contains only >= aspnetcore-10.0 content

  • Enhanced features list with memory management link
  • Get started and Additional resources sections
  • Uses not-latest-version-without-not-supported-content.md include

• Kestrel 6.x include (kestrel6.md): Split moniker ranges to provide version-appropriate content

  • >= aspnetcore-8.0 <= aspnetcore-9.0: Enhanced features list (without memory management)
  • >= aspnetcore-6.0 < aspnetcore-8.0: Original scenarios list
  • Ensures no overlap with main file moniker ranges

• Removed sections:

  • "Optional client certificates" from main overview and kestrel6.md include
  • Inline memory eviction content (now in dedicated article)
  • not-latest-version include reference from memory-management.md

• TOC: Added memory management article after Diagnostics

Moniker Strategy

The corrected moniker strategy uses the include file pattern to avoid overlapping ranges:

• kestrel.md: Only >= aspnetcore-10.0 (no overlap with include file)
• kestrel6.md include:
  • >= aspnetcore-8.0 <= aspnetcore-9.0 with enhanced features
  • >= aspnetcore-6.0 < aspnetcore-8.0 with original content
  • Earlier versions handled in subsequent ranges

This approach eliminates duplicate H2 headers and build warnings while ensuring:

• .NET 6-7: Shows original scenarios list
• .NET 8-9: Shows enhanced feature list without memory management
• .NET 10+: Shows enhanced feature list including memory management with link to new article

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/fundamentals/servers/kestrel.md	aspnetcore/fundamentals/servers/kestrel
aspnetcore/fundamentals/servers/kestrel/memory-management.md	aspnetcore/fundamentals/servers/kestrel/memory-management
aspnetcore/toc.yml	aspnetcore/toc

[wadepickett]

@tdykstra, looks like we hav an learning opporrtunity here for copilot. A moniker mishap, see build warning. Otherwise the PR looks great. Once figured out we can add the solution to the copilot instructions. Copilot did lay out its moniker strategy above in the description and so it was following our repo level instruction set so that is good at least.

[wadepickett]

Moniker issues, see build warnings. Dupe H2's etc as a result.

[tdykstra]

@copilot Copilot manipulated monitor tags. The result worked correctly according to what was written in the issue, but the build reported errors in the way the moniker tags were used. Can you correct the moniker tag errors while still producing the effect the issue called for?

[Copilot]

@copilot Copilot manipulated monitor tags. The result worked correctly according to what was written in the issue, but the build reported errors in the way the moniker tags were used. Can you correct ...

Fixed in commit 73e5f4d. The issue was duplicating entire sections within separate moniker ranges. Changed to use a single >= aspnetcore-8.0 range for common content, with a nested >= aspnetcore-10.0 range only for the memory management bullet point that differs.

[tdykstra]

@copilot The build is still reporting warnings with the revised moniker tag strategy. Can you please take another look?

[Copilot]

@copilot The build is still reporting warnings with the revised moniker tag strategy. Can you please take another look?

Fixed in commit c0dbc36. The issue was that my >= aspnetcore-8.0 range in kestrel.md overlapped with the >= aspnetcore-6.0 <= aspnetcore-9.0 range in the kestrel6.md include file, causing duplicate headers for versions 8-9.

The solution: kestrel.md now only has >= aspnetcore-10.0 content, and I split the kestrel6.md range into two:

• >= aspnetcore-8.0 <= aspnetcore-9.0 with enhanced features list
• >= aspnetcore-6.0 < aspnetcore-8.0 with original scenarios list

This eliminates all overlaps while achieving the goal of showing enhanced features for .NET 8+.

[wadepickett]

@tdykstra, build warnings with this include involved, but it is not claer to me what is going on:

[!INCLUDE]

[tdykstra]

@copilot The build is still reporting warnings. To fix them, please delete the reference to the not-latest-version.md Include file and replace it with not-latest-version-without-not-supported-content.md

[Copilot]

@copilot The build is still reporting warnings. To fix them, please delete the reference to the not-latest-version.md Include file and replace it with` not-latest-version-without-not-supported-conte...

Fixed in commit e7539d2. Replaced the not-latest-version.md include reference with not-latest-version-without-not-supported-content.md in both kestrel.md and memory-management.md files.

[tdykstra]

Fixed in commit e7539d2. Replaced the not-latest-version.md include reference with not-latest-version-without-not-supported-content.md in both kestrel.md and memory-management.md files.

@copilot Please revert this change in the memory management file

[Copilot]

Fixed in commit e7539d2. Replaced the not-latest-version.md include reference with not-latest-version-without-not-supp...

Reverted in commit 3717c27. The memory-management.md file now uses not-latest-version.md while kestrel.md continues to use not-latest-version-without-not-supported-content.md.

[tdykstra]

@copilot Please delete the reference to the include file not-latest-version in the memory -management file

[Copilot]

@copilot Please delete the reference to the include file not-latest-version in the memory -management file

Deleted in commit 462b650. The not-latest-version include reference has been completely removed from memory-management.md.

[tdykstra]

@copilot @cdopilot I would like that change that we just made go into the same pull request that we have been working with but I don't see it showing up there.

[Copilot]

@copilot @cdopilot I would like that change that we just made go into the same pull request that we have been working with but I don't see it showing up there.

The change is already in the PR. Commit 462b650 was successfully pushed to the copilot/update-kestrel-overview-content branch. You can see it in the commit history - it's the most recent commit that removed the not-latest-version include reference from memory-management.md.

[tdykstra]

@copilot With each of the previous commits I saw a build automatically show up in the PR output -- I don't see a build this time.

[Copilot]

@copilot With each of the previous commits I saw a build automatically show up in the PR output -- I don't see a build this time.

The commit 462b650 has been successfully pushed to the remote branch. CI/build triggers are managed by GitHub Actions and should start automatically. The build may be queued or processing - you can check the "Checks" tab in the PR or the "Actions" tab in the repository to see the build status. Sometimes there can be a delay before builds appear, especially if other workflows are running.