explicitly detect BuildFinishedEventArgs and return from pipe reading

[ltcmelo]

Hi @daveaglick , I recently upgraded to 3.0.0 (and 3.0.1) of Buildalyzer but bumped into an issue:

• the MSBuild pipe logger is hanging for certain apps of my testing pipeline.

Interestingly, all cases where I spotted the problem were upon a BuildFinishedEventArgs. So a temporary "solution" I found was to explicitly detect such event and return upon it.

This does not eliminate the hanging, but at least it allows for me reach the a finally in my Main function and call Environment.Exit(code).

Do you have any idea of what could be going on?

[ltcmelo]

Hi… I'm wondering whether there is an intend to merge this PR?

I seems that, with .NET 5, more projects are suffering from this hanging issue upon a IProjectAnalyzer.Build(). I added another open source app in the buildalyzer project.

[daveaglick]

Yes, I will definitely take a look at this PR soon. It’s summer and I’ve been on vacation so open source time has been limited recently.

[daveaglick]

Thanks for taking a look at this @ltcmelo!

Between the changes to the solution file, the modification of the project URL and author (for future reference, changes to package metadata should usually be discussed with package authors before modifying in a PR, especially when changing something like the project URL), and updating the target higher than it needed to be in this PR, I've merged in #6 which just isolates the BuildFinishedEventArgs bit.

Sorry it took so long to get back here - out of sight and out of mind and all that. I'm planning a new MsBuildPipeLogger and Buildalyzer release later today that should resolve your original issue.