Trimming provides similar Xamarin experience in .NET 6

[agocke]

Mono and CoreCLR continue to increase code sharing and Xamarin is moving to consume more of the .NET Core surface area.

Goals

• Trimmed Xamarin apps using .NET 6 produce similar behavior as before
• Trimmed Xamarin apps with .NET 6 are roughly the same size
• Xamarin apps produce minimal linker warnings and only for linker-unsafe constructs

Work

• Investigate representative Xamarin app with trimming enabled
  • App still works
  • Catalog and remove warnings
  • Investigate with custom trim steps disabled

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @vitek-karas, @agocke, @CoffeeFlux
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Mono and CoreCLR continue to increase code sharing and Xamarin is moving to consume more of the .NET Core surface area.

Goals

• Trimmed Xamarin apps using .NET 6 produce similar behavior as before
• Trimmed Xamarin apps with .NET 6 are roughly the same size
• Xamarin apps produce minimal linker warnings and only for linker-unsafe constructs

Work

• Investigate representative Xamarin app with trimming enabled
  • App still works
  • Catalog and remove warnings
  • Investigate with custom trim steps disabled

Author:	agocke
Assignees:	-
Labels:	Priority:0, User Story, area-AssemblyLoader-coreclr, linkable-framework
Milestone:	-

[marek-safar]

@jeffschwMSFT please don't tag user stories which have nothing to do with assembly loader with that area it's very confusing on the planning

[jeffschwMSFT]

would you prefer meta? I am fine either way.

[marek-safar]

yep, certainly meta

[marek-safar]

I think we should close this issue, it duplicates existing users stories #44654 and #43078

[jeffschwMSFT]

It feels distinct to me. This is an engineering tracking list of work. I agree these should be linked together in a coherent way. I see these items as a balance between engineering efficiency and tracking. If it is more efficient to have them separate, I am ok with that.

[marek-safar]

Yes, this is engineering tracking and not user-story and we already track them elsewhere in more details

[agocke]

@marek-safar Can you point me to those issues? I'm trying to build up a list of all Pri:0 linker items for Xamarin in .NET 6

[agocke]

#43078 and #44317 seem sufficient -- they cover the user experience for trimming, and size in the second one. Closing in favor of those issues