When running MSBuild static graph restore display additional log messages when project format is not known to MSBuild #4126
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.
Bug
Fixes: NuGet/Home#10363
Regression? Last working version:
Description
MSBuild static graph restore silently ignores projects in solution whose format is not known to MSBuild. Added following log messages which will be displayed at
Normal
verbosity.The solution did not have any projects to restore, ensure that all projects are known to be MSBuild and that the projects exist.
message will be logged when solution file doesn't have any projects to restore.The solution contains {count} project(s) "{list of projects}" that are not known to MSBuild. Ensure that all projects are known to be MSBuild before running restore on the solution.
message will be logged when a solution has projects whose format is not known to MSBuild.For some reason, MSBuild verbosity argument is not passed to NuGet. Hence NuGet always runs static graph restore logic in
Normal
verbosity. It is very much possible that I am missing something. Happy to learn based on the feedback from the team.NuGet.Client/src/NuGet.Core/NuGet.Build.Tasks.Console/MSBuildStaticGraphRestore.cs
Line 59 in 5d43a9c
PR Checklist
PR has a meaningful title
PR has a linked issue.
Described changes
Tests
Documentation