Skip to content

Should we reconsider our default suggestions for netstandard2.0? #47458

@baronfel

Description

@baronfel

Type of issue

Feedback

Description

The default assumption on our suggestions for cross-targeting are to start from netstandard2.0.

Is this good/relevant advice anymore? To me, a good default for a library author is something more like net6.0, and only in cases of requiring framework support or VS would you ever consider a netstandard2.0 target. Especially as we're trying to make a push ecosystem-wide for enabling features like AOT, I worry that a default of such an common-denominator TFM will result in library authors writing libraries that

  1. don't use modern .NET idioms, and
  2. inadvertently block the use of AOT/Trimming related tech

cc @richlander @agocke @jaredpar @ericstj for thoughts here.

Page URL

https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/cross-platform-targeting

Content source URL

https://github.com/dotnet/docs/blob/main/docs/standard/library-guidance/cross-platform-targeting.md

Document Version Independent Id

aff99d6b-9471-9277-160b-670ee8028b53

Platform Id

dc4d5a4c-4372-8ec5-e1f2-e3aa9f99e754

Article author

@JamesNK

Metadata

  • ID: 5b3638c9-ea3c-1c9e-2763-5c3e8e965663
  • PlatformId: dc4d5a4c-4372-8ec5-e1f2-e3aa9f99e754
  • Service: dotnet-fundamentals

Related Issues

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions