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.

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

Double clicking on NuGet warnings and errors in the Error list window does not open the source #5748

Open
mishra14 opened this issue Aug 11, 2017 · 1 comment
Labels
Functionality:Restore Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Product:VS.Client
Milestone

Comments

@mishra14
Copy link
Contributor

Currently, when NuGet throws warnings and errors in VS, the dotnet sdk picks them up from the assets file and replays them in the VS error list window.

However, even with the file path, double clicking the error or warning does not take the user to source of the problem.

@mishra14
Copy link
Contributor Author

I will reach out to the sdk folks to see if we need to fix something on our side.

@nkolev92 nkolev92 modified the milestones: 4.4, Backlog Nov 9, 2017
@jeffkl jeffkl added Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. and removed Pipeline:Icebox labels Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:Restore Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Product:VS.Client
Projects
None yet
Development

No branches or pull requests

5 participants