Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 23, 2026

Backport of #120477 to release/10.0

/cc @jkoritzinsky @jtschuster

Customer Impact

  • Customer reported
  • Found internally

Type maps created with the new System.Runtime.InteropServices.TypeMapAttribute would fail to work across assemblies as described when the user publishes their app with PublishTrimmed set to true. This affects our partner teams who want to take advantage of this API (.NET for Android, CsWinRT).

Regression

  • Yes
  • No

This was a new API in .NET 10

Testing

Many unit tests were added

Risk

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

Low. This only affects a new API in .NET 10 and is a targeted fix with included testing,

IMPORTANT: If this backport is for a servicing release, please verify that:

  • For .NET 8 and .NET 9: The PR target branch is release/X.0-staging, not release/X.0.
  • For .NET 10+: The PR target branch is release/X.0 (no -staging suffix).

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

jtschuster and others added 7 commits January 23, 2026 19:35
- Mark TypeMapAssemblyTargetAttributes when a typemapuniverse is marked
- Recurse through TypeMapAssemblyTarget assemblies to find all TypeMapAttributes
- Refactor TypeMapHandler construction and initialization
- Use TypeReferenceEqualityComparer for Dictionaries
- Add more test coverage
…ap.cs

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@github-actions github-actions bot requested a review from marek-safar as a code owner January 23, 2026 19:35
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Jan 23, 2026
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.

@Sergio0694
Copy link
Contributor

Somehow we missed this one, I thought it had already been cherry-picked. Thank you @AaronRobinsonMSFT! 😅

Copy link
Member

@JulieLeeMSFT JulieLeeMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@JulieLeeMSFT JulieLeeMSFT added the Servicing-consider Issue for next servicing release review label Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-System.Runtime.InteropServices linkable-framework Issues associated with delivering a linker friendly framework Servicing-consider Issue for next servicing release review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants