Jan Krivanek

Or there is another - more conservative - approach: send props on ProjectStartedEventArgs if all loggers are legacy, send them on ProjectEvaluationFinishedEventArgs if all loggers are enlightened and in the...

The original requirement from the security review was to be able to locate all the check names (and respective package names that contained them) that were enabled in the build,...

There is no strong consesus on value and even need for this change - so considering nonzero risk of the change - I'm rather pulling this out. There were some...

For easier investigation - we'd need the failure logs and communication logs. You can collect those by setting `MSBUILDDEBUGCOMM` env var to 1 and (optionally, but recommended) `MSBUILDDEBUGPATH` to an...

Possibly related: https://github.com/dotnet/msbuild/issues/10315

Btw. - the: * the IsEnabled property should support enabled as well * a severity of None (also, none) should be allowed to disable a rule (this is in line...

The `ProjectInstance` (or `Project`) can be created and evaluated standalone. They can then be used to issue build requests. That's how those 2 events get executed separately. I'll double/triple check...

Reopening as fix introduced VS perf regression - we will need to fix that one in coordination with the fix

We'll need to investigate the hidden root-cause, in order to prevent the perf regression after fix. **First we'll need to find stable repro - steps:** * Create simple console app...

Thank you @GangWang01! Let's dig more into why the fix for this causes perf regression - what are the other registered loggers in VS and what are their setting of...