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

If package failed to restore, error should be printed i the output even with Minimal verbosity ON #5658

Closed
abpiskunov opened this issue Jul 27, 2017 · 5 comments
Labels
Milestone

Comments

@abpiskunov
Copy link

Please read the following information before posting the issue.

Details about Problem

Latest d15rel.

Detailed repro steps so we can see the same problem

  1. When you have some unknwon package in the project an restore it just prints this:

Restoring NuGet packages...
NuGet package restore failed.
Time Elapsed: 00:00:02.7078836
========== Finished ==========

Yes, there is an error in the error list, but when build happens it does print errors in the output along with adding errors to Error list, but restore does not - it is inconsistent. Also, very often i have error list hidden with Output pane on top (active when docked) and i have to do extra clicks to go to error list (if will remember that error might be there at the moment..). I don't want to "think", but see it immediately ...

Other suggested things

Verbose Logs

Please include verbose logs (NuGet.exe -verbosity detailed | dotnet.exe --verbosity diag | etc...)

Sample Project

Very helpful if you can zip a project and paste into this issue!

@emgarten emgarten added this to the 4.4 milestone Jul 28, 2017
@emgarten
Copy link
Member

This is similar to #5412

I think we should consider bringing the output window details back.

@abpiskunov
Copy link
Author

yes #5412 looks exactly what i meant :).

@rrelyea rrelyea added Triage:NeedsTriageDiscussion Type:DCR Design Change Request Type:Bug and removed Type:DCR Design Change Request labels Aug 7, 2017
@rrelyea
Copy link
Contributor

rrelyea commented Aug 7, 2017

@anangaur - c# compilation shows errors in the output window and error list. should we do the same? can you please do a quick review and give your suggestion?
Or should we show the error window, every time?

@abpiskunov
Copy link
Author

abpiskunov commented Aug 7, 2017

(btw showing/poping error window or other tool windows everytime is annoying and this pattern is avoided in other places in core and web project system)

@emgarten emgarten modified the milestones: 4.4, Backlog, 4.5 Oct 19, 2017
@emgarten emgarten added the Resolution:Duplicate This issue appears to be a Duplicate of another issue label Oct 19, 2017
@emgarten
Copy link
Member

Duplicate of #6047

The above is a more general case, so going with that one.

Let me know if these are different requests, but it seems like the root cause of both is that NuGet isn't writing errors to the output pane.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants