Skip to content

Explore alternatives for avoiding packaging shared framework into dotnet-watch package #26993

Closed
Closed
Explore alternatives for avoiding packaging shared framework into dotnet-watch package#26993
Labels
affected-very-fewThis issue impacts very few customersarea-commandlinetoolsIncludes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPIseverity-nice-to-haveThis label is used by an internal tooltask
Milestone
Test failures

Description

@captainsafia
captainsafia
opened on Oct 17, 2020

Instead of #24816, we should look into configuring the packaging for dotnet-watch so that only relevant files are copied, similar to what is done in the Blazor dev server.

Activity

  1. captainsafia
    added
    area-commandlinetoolsIncludes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI
    task
    on Oct 17, 2020
  2. mkArtakMSFT
    added this to the Next sprint planning milestone on Oct 22, 2020
  4. jkotalik
    added
    affected-very-fewThis issue impacts very few customers
    severity-nice-to-haveThis label is used by an internal tool
    on Nov 9, 2020

  5. pranavkm commented on Jun 4, 2021

    @pranavkm
    pranavkm
    on Jun 4, 2021
    Contributor

    This is no longer an issue for watch.

  6. pranavkm
    closed this as completedon Jun 4, 2021
  7. ghost locked as resolved and limited conversation to collaborators on Jul 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    affected-very-fewThis issue impacts very few customersarea-commandlinetoolsIncludes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPIseverity-nice-to-haveThis label is used by an internal tooltask

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions