Skip to content

Improve workload list to work better with VS and other SDK bands #31283

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
Open
3 tasks
marcpopMSFT opened this issue Mar 17, 2023 · 1 comment
Open
3 tasks

Improve workload list to work better with VS and other SDK bands #31283

marcpopMSFT opened this issue Mar 17, 2023 · 1 comment
Labels
Area-Workloads Cost:S Less than 4 person weeks of work per central guidance Priority:1 Work that is critical for the release, but we could probably ship without User Story A single user-facing feature. Can be grouped under an epic.
Milestone
8.0.4xx

Comments

@marcpopMSFT
Copy link
Member

marcpopMSFT commented Mar 17, 2023 •
edited
Loading

  • workload list should apply to other patch versions in the same feature band for VS workloads
  • workload list should print message suggesting dotnet workload update --from-previous-sdk if no workloads are currently installed but they are installed in a previous feature band (See [NETSDKE2E]Workloads are not displayed in "dotnet workload list" after upgrade from NET8 preview 1 to NET8 preview 2 SDK. installer#15683)
  • It's possible to get into a state today where dotnet workload list lists a set of workloads but the manifests have been updated ahead of the packs. We should investigate options for improving list to detect this situation (either do deeper look into the installation records or do a deeper check on the packs). We need to be careful this doesn't break the VS install logic as well.
@marcpopMSFT marcpopMSFT mentioned this issue Mar 17, 2023
Open
17 tasks
@ghost ghost added Area-Workloads untriaged Request triage from a team member labels Mar 17, 2023
@marcpopMSFT marcpopMSFT changed the title should apply to other patch versions in the same feature band for VS workloads Improve workload list to work better with VS and other SDK bands Mar 17, 2023
@marcpopMSFT marcpopMSFT added User Story A single user-facing feature. Can be grouped under an epic. and removed untriaged Request triage from a team member labels Mar 17, 2023
@marcpopMSFT marcpopMSFT added this to the 8.0.1xx milestone Mar 17, 2023
@marcpopMSFT marcpopMSFT added Cost:S Less than 4 person weeks of work per central guidance Priority:1 Work that is critical for the release, but we could probably ship without labels Mar 17, 2023
@nagilson
Copy link
Member

workload list should apply to other patch versions in the same feature band for VS workloads

If we don't need to spawn a new resolver, I think this would be resolved by the changes in: #30266

@marcpopMSFT marcpopMSFT modified the milestones: 8.0.1xx, 8.0.2xx Sep 15, 2023
@marcpopMSFT marcpopMSFT modified the milestones: 8.0.2xx, 8.0.4xx Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Workloads Cost:S Less than 4 person weeks of work per central guidance Priority:1 Work that is critical for the release, but we could probably ship without User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Milestone
8.0.4xx
Development

No branches or pull requests
2 participants
@marcpopMSFT @nagilson