-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
🏁 Release: .NET Core 2.xIdentifies work items for the .NET Core 2.x releasesIdentifies work items for the .NET Core 2.x releasesPri1Indicates issues/PRs that are high priorityIndicates issues/PRs that are high priorityPri3Indicates issues/PRs that are low priorityIndicates issues/PRs that are low priorityarea-MetaConcerns something that extends across runtime area boundaries, for example, IDisposable.Concerns something that extends across runtime area boundaries, for example, IDisposable.cross-platformIndicates issues or PRs that relate to content applicable to both Framework and Core.Indicates issues or PRs that relate to content applicable to both Framework and Core.doc-updateUpdate outdated articlesUpdate outdated articles
Description
APIs might have a different behavior depending on the platform in .NET Core and might throw the PlatformNotSupported exception. We need to call that out in the Exception section of the APIs impacted.
I remember seeing spreadsheets flowing around with that information @terrajobst. Do we have the latest version of that @terrajobst?
/cc @bartonjs
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
🏁 Release: .NET Core 2.xIdentifies work items for the .NET Core 2.x releasesIdentifies work items for the .NET Core 2.x releasesPri1Indicates issues/PRs that are high priorityIndicates issues/PRs that are high priorityPri3Indicates issues/PRs that are low priorityIndicates issues/PRs that are low priorityarea-MetaConcerns something that extends across runtime area boundaries, for example, IDisposable.Concerns something that extends across runtime area boundaries, for example, IDisposable.cross-platformIndicates issues or PRs that relate to content applicable to both Framework and Core.Indicates issues or PRs that relate to content applicable to both Framework and Core.doc-updateUpdate outdated articlesUpdate outdated articles