dotnet new console
dotnet msbuild /fl /flp:vebosity=diagnostic /clp:verbosity=diagnostic > out
Expected behavior
out and msbuild.log contain evaluation started / ended events which wrap around the events coming from that evaluation (evaluation events get indented one level deeper under the evaluation started / ended events)
Actual behavior
The log files do not contain these events
Cause
It seems the FileLogger does not log all events, it treats each event type separately. The evaluation started / ended events slip through the cracks and do not get logged. The binary logger does write them out, because it does not discriminate on the event type.
Not really sure if this is appropriate for you @Forgind, but I will let you try it out and let me know if you need to learn some more before tackling an issue like this.
Steps to reproduce
Expected behavior
out and msbuild.log contain evaluation started / ended events which wrap around the events coming from that evaluation (evaluation events get indented one level deeper under the evaluation started / ended events)
Actual behavior
The log files do not contain these events
Cause
It seems the FileLogger does not log all events, it treats each event type separately. The evaluation started / ended events slip through the cracks and do not get logged. The binary logger does write them out, because it does not discriminate on the event type.