Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Closed
captainsafia opened this issue Oct 17, 2020 · 2 comments
Closed

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

captainsafia opened this issue Oct 17, 2020 · 2 comments
Labels
affected-very-few This issue impacts very few customers area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI severity-nice-to-have This label is used by an internal tool task
Milestone
Test failures

Comments

@captainsafia
Copy link
Member

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.
@captainsafia captainsafia added area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI task labels Oct 17, 2020
@mkArtakMSFT mkArtakMSFT added this to the Next sprint planning milestone Oct 22, 2020
@ghost
Copy link

ghost commented Oct 22, 2020

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@jkotalik jkotalik added affected-very-few This issue impacts very few customers severity-nice-to-have This label is used by an internal tool labels Nov 9, 2020 — with ASP.NET Core Issue Ranking
@pranavkm
Copy link
Contributor

pranavkm commented Jun 4, 2021

This is no longer an issue for watch.

@pranavkm pranavkm closed this as completed Jun 4, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jul 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affected-very-few This issue impacts very few customers area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI severity-nice-to-have This label is used by an internal tool task
Projects
None yet
Milestone
Test failures
Development

No branches or pull requests
4 participants
@pranavkm @captainsafia @jkotalik @mkArtakMSFT