Merged
Conversation
davkean
approved these changes
Dec 6, 2017
Pilchie
approved these changes
Dec 7, 2017
Member
|
BTW - What determines if this log is enabled? Is there a way for customers to collect our logs when things go wrong? |
Member
|
Enabled by default in DEBUG builds, otherwise, a new category shows up in the Output window when environment is set |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add logging for NuGetRestorer to capture information sent to NuGet during nomination
Customer scenario
To assist investigations of problems in interactions between project-system and NuGet, add logging to specify what information is sent. Users can turn on logging with existing
set PROJECTSYSTEM_PROJECTOUTPUTPANEENABLED=1flagRisk and Performance impact
None, only active when debugging flag is on
/cc @dotnet/project-system