What does the fix do?
-add extra check if _fscArguments already contains data, since only the first BuildMessageEventArgs to pass my checks contains the data we want.
How debugging went:
I printed all BuildMessageEventArgs senders and messages.
With SkipCompilerExecution I would expect 1 event. There are however multiple, all from the Fsc process, this leads to _fscArguments being overridden with the new data. In this example that would be: ["","The command exited with code 1."]
https://github.com/daveaglick/Buildalyzer/issues/151
What does the fix do? -add extra check if _fscArguments already contains data, since only the first BuildMessageEventArgs to pass my checks contains the data we want.
How debugging went: I printed all BuildMessageEventArgs senders and messages. With SkipCompilerExecution I would expect 1 event. There are however multiple, all from the Fsc process, this leads to _fscArguments being overridden with the new data. In this example that would be: ["","The command exited with code 1."]