Skip to content
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

Design Package Source mapping package installation experiences epic #10730

Open
2 of 5 tasks
nkolev92 opened this issue Apr 5, 2021 · 3 comments
Open
2 of 5 tasks

Design Package Source mapping package installation experiences epic #10730

nkolev92 opened this issue Apr 5, 2021 · 3 comments
Assignees
@JonDouglas
Labels
Area:PackageSourceMapping Issues related to the package source mapping feature Epic Functionality:Install The install command in VS/nuget.exe Priority:2 Issues for the current backlog. Product:dotnet.exe Product:VS.Client Triage:NeedsDesignSpec Type:Spec

Comments

@nkolev92
Copy link
Member

nkolev92 commented Apr 5, 2021 •
edited
Loading

Follow up to #6867 and #10660.

#10660 talks about the MVP, primarily focusing on the restore experience and not the PM UI, PMC & dotnet add package experience.

fyi @JonDouglas
@JonDouglas
Copy link
Contributor

I'll start to work on these experiences as we progress in the MVP.

@nkolev92 nkolev92 added the Area:PackageSourceMapping Issues related to the package source mapping feature label Apr 6, 2021
@nkolev92 nkolev92 removed their assignment Jun 22, 2021
@nkolev92
Copy link
Member Author

Removing my assignment.

@JonDouglas has made good progress here and vetted initial designs.

@nkolev92 nkolev92 changed the title Design namespaces filtering in the package installation experiences (VS PM UI, PMC & dotnet add package) Design Package Source mapping package installation experiences (VS PM UI, PMC & dotnet add package) Sep 30, 2021
@nkolev92 nkolev92 mentioned this issue Nov 6, 2021
Closed
10 tasks
@nkolev92
Copy link
Member Author

nkolev92 commented Nov 6, 2021

I think task can be broken down into 4 (maybe 4 separate issues? we can discuss).

  • Package Manager UI - installation, sources view, browse etc.
  • NuGet Options UI - Adding free hand mappings, remove mappings, marking sources as fallback with *
  • NuGet PMC - installation, Find-Package etc.
  • dotnet add package - installation/updates etc.

@nkolev92 nkolev92 mentioned this issue Nov 6, 2021
Open
21 tasks
@nkolev92 nkolev92 added the Epic label Nov 12, 2021
This was referenced Nov 12, 2021
Closed
Closed
Open
Open
@nkolev92 nkolev92 changed the title Design Package Source mapping package installation experiences (VS PM UI, PMC & dotnet add package) Design Package Source mapping package installation experiences epic Nov 19, 2021
This was referenced Feb 7, 2022
Closed
Closed
@JonDouglas JonDouglas mentioned this issue Feb 3, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JonDouglas JonDouglas

Labels
Area:PackageSourceMapping Issues related to the package source mapping feature Epic Functionality:Install The install command in VS/nuget.exe Priority:2 Issues for the current backlog. Product:dotnet.exe Product:VS.Client Triage:NeedsDesignSpec Type:Spec
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@JonDouglas @nkolev92 @heng-liu