-
Notifications
You must be signed in to change notification settings - Fork 795
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
Use MSBuild's logging facilities instead of writing to console. #13896
Conversation
Hi, this is good staff. |
Oh, didn't see the CI failures. Sure, go ahead, thanks. |
@KevinRansom : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit of unknown territory for me yet so my comments might be irrelevant a bit :)
Generally using the built-in logging mechanism instead of printfs everywhere is a right thing to do so I think this should get in - my comments are mostly about other changes here.
The repository's MSBuild tasks log messages directly to the console, which is more verbose than needed, cannot be made less verbose, and does not play well with MSBuild's logging facilities.
This PR changes the tasks to use the Lawful Good™ way of logging events. Also instead of implementing the
Microsoft.Build.Framework.ITask
interface, they now inherit theMicrosoft.Build.Utilities.Task
class, which is easier to use.