Revert "Make build property CompilerGeneratedFilesOutputPath accessible to Roslyn project" #9579
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #9544
This change was triggering a failure in Roslyn around use of
EmitCompilerGeneratedFiles
, leading to project faults resembling:At the start of October, Roslyn started requiring an absolute path here:
https://github.com/dotnet/roslyn/pull/75311/files#diff-8440787c9215f81fa8cabe9072d5ab0598251313a4480cfca075041ceed8a5bbR41-R44
But by default, the SDK provides a relative path (and indeed all online examples show relative paths here). Only once we inserted #9544
@tmat has a PR open in Roslyn to fix this: https://github.com/dotnet/roslyn/pull/75674/files
Once the Roslyn side is fixed, we can reinstate this change.
Microsoft Reviewers: Open in CodeFlow