MSBuild data should not be passed between tasks via static fields #364
Description
The following static field access should be rewritten using MSBuild inputs and outputs:
I believe the most straightforward and reliable implementation would involve generating GUIDs and/or temporary file names within MSBuild, and then passing those names to the build tasks. With this approach, the instrumentation task would produce known outputs for a given set of inputs, which can be tracked by the MSBuild targets.
📝 This limitation forces test execution to use /m:1 since the static property cannot keep track of information from multiple test executions in parallel.