Uh oh!
There was an error while loading. Please reload this page.
[release/8.0-rc1] Add missing type forwards - #90673
Conversation
Fixes#90578 IDispatchImplAttribute, IDispatchImplType and SetWin32ContextInIDispatchAttribute were removed with 9f1dd1a and 26a91ad Those dropped types weren't flagged because APICompat only validates reference assemblies. We have three implementation only shim assemblies: mscorlib, System and System.Data. I verified that no other type forwards were lost between .NET 7 and .NET 8.
ghost
commented
Aug 16, 2023
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #90669 to release/8.0-rc1 /cc @ViktorHofer Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
carlossanlop
commented
Aug 16, 2023
Approved by Tactics via email. Assuming all feedback in the |
ViktorHofer
commented
Aug 16, 2023
Ready to merge in for .NET 8 to fix the regression. Further discussions in the main PR shouldn't affect this backport. |
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,RegistrationClassContextorRegistrationConnectionTypetypes 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.