[ericstj]

This is first draft. I might be assuming too much familiarity with the problem space. Please provide feedback 🤝

---

Internal previews

File	Preview link
docs/standard/library-guidance/dependencies-net.md	Learn preview
docs/standard/library-guidance/toc.yml	Learn preview

Build report

[Copilot]

Pull Request Overview

This PR introduces comprehensive guidance for .NET library authors on selecting dependency versions when targeting multiple .NET framework versions. The document outlines three primary strategies (latest supported versions, TFM-specific versions, and branching), their tradeoffs, and provides concrete recommendations with code examples.

Key changes:

• New guidance document explaining dependency version selection strategies for .NET libraries.
• Decision matrix comparing engineering, servicing, and update friction costs across strategies.
• Code examples demonstrating each approach using System.Text.Json references.

[ericstj]

I've addressed all feedback, please have another pass at this. Thank you.

[BillWagner]

@ericstj Do you want to address the remaining comments, or should I close this?

[ericstj]

Let me have a look, I'm working in a different space these days, but this doc needs to exist. Let me get it in.

[ericstj]

@BillWagner I addressed feedback, PTAL

[Copilot]

🟡 Changes recommended

The example selects vulnerable System.Text.Json 8.0.0, which runtime servicing will not replace on net6.0/net7.0, and the support-lifetime guidance could lead to incorrect servicing plans.

2 open issues

• Use a serviced System.Text.Json version and explain patching older branches · New
• Clarify which LTS release shares the STS end-of-support date · New

_{Review effort: Balanced}

[ViktorHofer]

@ericstj thanks for finishing the doc. Very much appreciated 👍