Feature: Support AOT across Dapr clients

[c-ramin]

Expected Behavior

In a project where subscriptions are made via the bus using .WithTopic("name", nameof(class)), I would like the MapSubscribeHandler to work correctly in AOT (Ahead-Of-Time) mode.
Currently, it seems that AOT is not fully supported in this scenario, which leads to issues when using Dapr with this pattern. It would be great if this functionality could be improved to support AOT seamlessly.

Actual Behavior

At startup, the application throws the following error, which I believe is related to the Subscription class in the following line of code:
https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.AspNetCore/DaprEndpointRouteBuilderExtensions.cs#L189

Steps to Reproduce the Problem

=> Project c# 9 aot
=> Juste add enpoint with WithTopic
=> and use compoenent type: pubsub.rabbitmq
=> Start service

Release Note

RELEASE NOTE: FIX support AOT when subscribing with the bus

[WhitWaldo]

@c-ramin To my knowledge, none of the Dapr .NET SDK is compatible with AOT (at least not intentionally - it's not something we test for), but it's certainly something we can look at adding in an upcoming release.

[c-ramin]

Thank you again for your response. To my knowledge, the client (http) dapr part works correctly in native mode with AOT. However, in my case, subscriptions are the primary feature I'm interested in. I would be delighted if Dapr could consider supporting this in a future release.

[WhitWaldo]

@c-ramin Certainly - using the HTTP API doesn't utilize any of the Dapr .NET SDK bits, so you're just using .NET functionality itself which is certainly optimized for AOT.

We're wrapping up 1.15 right now but I'll do some research on what's involved.