Mono Componentization

[lambdageek]

This is a project about delivering optional features with the Mono runtime as pieces that can be included or omitted by the workload for particular scenarios.

Tasks

Initial lift

• Design document - code organization [design] Mono runtime components #49913
• Initial implementation Mono runtime component infrastructure including EventPipe/DiagnosticsServer as a Mono runtime component. #50837 - static components only
• Dynamic components
• Design an MSBuild protocol between runtime pack and workloads Define Mono runtime components build tooling for the workloads #54417
  • Generate a .props file describing the components into the runtime pack
  • Default targets for describing which native libs to link given the selected components
• Runtime functional tests

Components

• Diagnostic Server & EventPipe
• Hot Reload - PR [mono] Componentize hot reload #52866

Followup work

• (moved to vNext Follow-on mono runtime componentization work #57131) Route eglib stateful functions (logging, allocators) from the components to the runtime

Bonus

• Move debugger to a component
• (moved to vNext Follow-on mono runtime componentization work #57131) Move the interpreter to a component (leverage existing libmono-ee-interp.a support)

End to end supported workloads:

• Browser [browser-wasm] Support Mono runtime components in workload #54565
• Android
• iOS Simulator
• iOS Device
• MacCatalyst

[lambdageek]

/cc @lateralusX @akoeplinger @steveisok

[lateralusX]

EventPipe/DiagnosticsServer need this support for .net6 on platforms where we use TCP transport in DiagnosticsServer (iOS/Android).

[lambdageek]

We need some uniform mechanism to update src/installer/pkg/sfx/Microsoft.NETCore.App/Directory.Build.props for the installer packaging of components. Adding individual manifest entries doesn't seem sustainable.

[lateralusX]

Initial implementation and use of static components on all platforms, done.

[CoffeeFlux]

We should estimate the size savings when compiling out the debugger to try and prioritize componentizing it.

[lateralusX]

Support for dynamic components done, currently Android runtime is configured to use dynamic instead of static components.

[steveisok]

@lambdageek Do you think we're good for what you wanted to get out of 6.0?

[lewing]

good for 6 from my side

[lambdageek]

Yea I think we're good for .net6. Moved the remaining work to a new issue #57131