[release/9.0-staging] Support generic fields in PersistedAssemblyBuilder #110839
+95
−9
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.
Backport of #110372 to release/9.0-staging
/cc @steveharter
Customer Impact
The new
PersistableAssemblyBuilder
functionality added in v9 has a bug where generic fields do not generate the proper IL, causing a generic field to be generated as non-generic.Regression
This was new functionality added in v9.
Testing
The original author's repro was verified and a test added that inspects the generated field's metadata to make sure the field is generic.
Risk
Low; the fix is fairly straightforward and follows other similar cases where we need to use metadata from open generic types instead of the closed generic type.