Skip to content

React to changes in Microsoft.NETCore.App #9720

Closed

Description

@natemcmaster

As a part of FrameworkReference refactoring, the packaging structure for Microsoft.NETCore.App will be changing to split into several packages. https://github.com/dotnet/core-setup/issues/4775 We need to update aspnet repos to consume the new package IDs.

The new package IDs:

  • Microsoft.NETCore.App.Ref
  • Microsoft.NETCore.App.Runtime.$(Rid)

Activity

  1. added this to the 3.0.0-preview6 milestone on Apr 24, 2019
  2. self-assigned this
    on Apr 24, 2019
  3. added
    blockedThe work on this issue is blocked due to some dependency
    on May 28, 2019
  4. natemcmaster commented on May 28, 2019

    @natemcmaster
    ContributorAuthor
  5. removed
    blockedThe work on this issue is blocked due to some dependency
    on Jun 12, 2019
  6. natemcmaster commented on Jun 12, 2019

    @natemcmaster
    ContributorAuthor

    Initial PR - dotnet/extensions#1828. If this is the right change (waiting for review from others), then it needs to be applied to all repos listed in the issue above.

  7. jkotalik commented on Jun 28, 2019

    @jkotalik
    Contributor

    Acceptance checklist (check one item)

    • We decided not to take this fix.
    • The fix is tests-only.
    • The fix contains product changes (check all items below).
      • Relevant XML documentation comments for new public APIs are present.
      • Narrative docs (docs.microsoft.com) are updated. (check one item below)
        • The change requires a new article. An issue with an outline has been filed here: [ISSUE LINK]
        • The change requires a change to an existing article. A docs PR with these changes is linked here: [PR LINK]
        • The change requires no docs changes.
      • Verification has been completed. (check one item below)
        • Let's just say, the product wouldn't build if this didn't work.
  8. added
    acceptedThis issue has completed "acceptance" testing (including accessibility)
    on Jun 28, 2019
  9. ghost locked as resolved and limited conversation to collaborators on Dec 3, 2019
  10. added
    area-infrastructureIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
    and removed
    feature-platformDeprecated: Cross-cutting issues related to ASP.NET Core as a platform
    on Jan 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

acceptedThis issue has completed "acceptance" testing (including accessibility)area-infrastructureIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions