Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add NetCoreAppCurrent config to where it's missing #54215

Merged
merged 2 commits into from
Jun 15, 2021

Conversation

ViktorHofer
Copy link
Member

This is addressing the following scenarios in order:

  • When there is a netcoreapp3.1 or net5.0 asset available in the lib,
    also add a NetCoreAppCurrent configuration to avoid PackageReferences
    to libraries that are inbox in net6.0 but not in previous .NetCoreApp
    versions. Examples are M.Win32.Registry which will be inbox soon.
  • When there's a NetCoreAppCurrent config in the lib but not in the ref,
    add it there as well to always resolve the ref of the current version.
  • When there are NetCoreAppCurrent rid specific configuration in the lib
    not a non-rid configuration, add one so that P2Ps from rid-less
    NetCoreAppCurrent configs in other projects, pick the
    NetCoreAppCurrent config from the lib and the ref.

Contributes to #54012

This is addressing the following scenarios in order:
- When there is a netcoreapp3.1 or net5.0 asset available in the lib,
  also add a NetCoreAppCurrent configuration to avoid PackageReferences
  to libraries that are inbox in net6.0 but not in previous .NetCoreApp
  versions. Examples are M.Win32.Registry which will be inbox soon.
- When there's a NetCoreAppCurrent config in the lib but not in the ref,
  add it there as well to always resolve the ref of the current version.
- When there are NetCoreAppCurrent rid specific configuration in the lib
  not a non-rid configuration, add one so that P2Ps from rid-less
  NetCoreAppCurrent configs in other projects, pick the
  NetCoreAppCurrent config from the lib and the ref.
@ghost
Copy link

ghost commented Jun 15, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

This is addressing the following scenarios in order:

  • When there is a netcoreapp3.1 or net5.0 asset available in the lib,
    also add a NetCoreAppCurrent configuration to avoid PackageReferences
    to libraries that are inbox in net6.0 but not in previous .NetCoreApp
    versions. Examples are M.Win32.Registry which will be inbox soon.
  • When there's a NetCoreAppCurrent config in the lib but not in the ref,
    add it there as well to always resolve the ref of the current version.
  • When there are NetCoreAppCurrent rid specific configuration in the lib
    not a non-rid configuration, add one so that P2Ps from rid-less
    NetCoreAppCurrent configs in other projects, pick the
    NetCoreAppCurrent config from the lib and the ref.

Contributes to #54012

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Infrastructure-libraries

Milestone: -

@ViktorHofer
Copy link
Member Author

CI is nearly finished. Merging to get one more change which depends on this in before we snap for P6.

@ViktorHofer ViktorHofer merged commit b90631f into dotnet:main Jun 15, 2021
@ViktorHofer ViktorHofer deleted the NormlaizeNetCoreAppOobs branch June 15, 2021 14:40
@ghost ghost locked as resolved and limited conversation to collaborators Jul 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants