Skip to content

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

@captainsafia

Description

@captainsafia

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.

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

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions