Csc task incorrectly forwarding info diagnostics to msbuild logger

[m0sa]

Version Used:

Microsoft (R) Visual C# Compiler version 2.9.0.63208 (958f235)
Copyright (C) Microsoft Corporation. All rights reserved.

Steps to Reproduce:

1. Create an arbitrary csproj with an analyzer that output at least one Info level diagnostic
2. Create a custom ILogger implementation that handles the IEventSource.MessageRaised event
3. Attach it to an msbuild execution, e.g. msbuild Project1.csproj /logger:ILogger.dll

Expected Behavior:
The ILogger gets a structured BuildMessageEventArgs, containing the parsed:

• BuildMessageEventArgs.Code = "INFO"
• BuildMessageEventArgs.File
• BuildMessageEventArgs.LineNumber
• BuildMessageEventArgs.ColumnNumber
• BuildMessageEventArgs.Message

Actual Behavior:

The BuildMessageEventArgs.Message contains the full line in the cannonical msbuild format.

---

The issue here is that Log.LogMessageFromText and CannonicalError only handle errors and warnings. I'm raising this issue here, since MSBuild has no notion of DiagnosticSeverity.Info.

[jaredpar]

This behavior is currently "By Design". The compiler doesn't output any informational diagnostics today: on the command line or via MSBuild. This is why they don't show up in the logger.

Why do you believe they should appear here? Note: the set of info diagnostics can change from version to version of the compiler. It's info. That's also part of the reason that we don't expose them. It's meant for host consumption only.

[gafter]

@m0sa Please reopen if you want to follow up here.

[AxelHu]

Now source generator is available as a new feature in .net 5, anyway for me to show non error/warning message in the output?