[release/8.0-rc1] Add missing type forwards #90673
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.
Backport of #90669 to release/8.0-rc1
/cc @ViktorHofer
Customer Impact
Customers migrating from .NET Framework to .NET who reference the
AssemblyRegistrationFlags
,ExporterEventKind
,PEFileKinds
,RegistrationClassContext
orRegistrationConnectionType
types would see an application crash because of aTypeLoadException
. Reason is that type forwards are missing from the mscorlib facade assembly.Testing
Manually tested by diffing the produced assembly via ILDasm.
Risk
Low. Type forwards are added to the mscorlib.dll assembly only. Other code isn't impacted.