Skip to content

Developers should be guided away from more obsolete APIs in .NET 6 #46767

@jeffhandley

Description

@jeffhandley

With #39269, we marked many APIs as [Obsolete] in .NET 5. Some follow-up infrastructure work was identified during and after that PR, and some other obsoletions have been proposed. With this story, we will:

  1. Complete that follow-up infrastructure work
  2. Consider additional APIs that could be marked as [Obsolete] (optionally with custom diagnostic Ids)
  3. Document those obsoletions
  4. Consider if there are places where a Roslyn Code Fixer should be provided for obsolete APIs

.NET 6 Work Items

Moved to Future

Definition of Done

Each obsoletion needs to have the following Definition of Done applied.

  • Pre-announce the upcoming breaking change to partner teams using our breaking change DL at least 2 weeks before merge
  • Use the Obsoletions.cs file to define the message and diagnostic ID
  • Add the obsoletion to the list of diagnostics
  • Announce the breaking change to our partner teams using our breaking change DL upon merge
  • Create the breaking change document issue
  • Register the aka.ms link for SYSLIBxxxx obsoletions (see @jeffhandley)

Metadata

Metadata

Labels

Bottom Up WorkNot part of a theme, epic, or user storyCost:LWork that requires one engineer up to 4 weeksPriority:2Work that is important, but not critical for the releaseUser StoryA single user-facing feature. Can be grouped under an epic.area-Meta

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions