Add BuildOM forward compatibility #10394
Merged
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.
Fixes #10349
Context
The OM unification work #10172 introduced backwards compatible unified OM (code compiled against old MSBuild binaries can be run against new MSBuild binaries), but it was not forward compatible (code compiled against new MSBuild binaries could not be run against old MSBuild binaries). This change is bridging such gap.
Changes Made
Adding 'proxy' properties for those that have been pulled to base classes - so that the compiled code is not trying to reference base classes, that do not exist in the old version of MSBuild code.
Testing
Manual testing of x-compatibility of the OM.
Notes
Big thanks to @rainersigwald and @dfederm for the detailed help and ideas during troubleshooting the problem