E2E scenario: ASP.NET minimal Web API applications can be NativeAOT compiled for size and performance

[samsp-msft]

We need to grow the list of workloads which are supported by NativeAOT. The target for .NET 8 should be to enable ASP.NET Minimal Web API applications to be supported for compiling for NativeAOT.

This is a follow on from #61231

The developer of those applications should be able to follow the standard patterns supported by minimal APIs, without major changes, such as needing to replace the DI container implementation. Any corner-case limitations should be flagged with compiler errors when the <PublishAot>true</PublishAot> flag is included.

This initiative will be driven by using a set of prototypical sample applications that need to work for NativeAOT. These include:
[ ] https://github.com/DamianEdwards/MinimalApiPlayground/tree/main/src/Todo.Dapper (The dapper ORM, not Dapr)
[ ] https://github.com/DamianEdwards/MinimalApiPlayground/tree/main/src/Todo.EFCore

[samsp-msft]

Related Items:

• Developers can safely trim ASP.NET apps to reduce their deployment payloads aspnetcore#27384
  • Developers can safely trim their apps which use Dependency Injection to reduce the size of their apps #44432
  • Improve trimming support for EF Core apps to reduce application size efcore#21894
• Native AOT in .NET 8 #69739
• Epic: .NET libraries are annotated to support trimming and we provide trimming guidance for library authors #43543

[samsp-msft]

Tagging @davidfowl, @vitek-karas, @agocke, @MichalStrehovsky, @jkotas, @eerhardt

[tommcdon]

Related diagnostic items:

• Developers can employ EventSource APIs when publishing for AOT targets to be able to use .NET tracing capabilities #43390
• Improve EventSource trimming #56154

[agocke]

Closing as the top-line goals for this are completed.