Conversation
| @@ -0,0 +1 @@ | |||
| /Isolate | |||
There was a problem hiding this comment.
The PR description is still the template/empty, but this change globally alters build behavior for the whole repo. Please update the PR description to include (1) why /Isolate is needed, (2) the expected user-facing impact (CLI build, VS build, CI), and (3) any measured improvement/regression you observed.
| @@ -0,0 +1 @@ | |||
| /Isolate | |||
There was a problem hiding this comment.
Adding /Isolate via Directory.Build.rsp applies it to all MSBuild executions (including local dev builds and IDE-driven builds), and may fail on environments where the MSBuild version doesn’t recognize the switch. If the intent is CI-only or limited-scope usage, consider moving this flag into the CI/build scripts instead of Directory.Build.rsp; otherwise, pin/standardize the build toolchain (e.g., via global.json and CI image/tooling updates) so all supported environments use an MSBuild version that supports /Isolate.
| /Isolate | |
| # /Isolate flag removed from global response file. | |
| # If isolation is required, pass /Isolate explicitly from CI or build scripts | |
| # instead of applying it to all MSBuild invocations via Directory.Build.rsp. |
No description provided.