Ryan Nowak

related: https://github.com/dapr/dotnet-sdk/pull/735

Thanks @dlemstra - I would have expected this to work as well. I was able to track down the documentation for this. https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-9.0/unconstrained-type-parameter-annotations I wonder if we need to use...

Note for myself in the future - when we do start rolling this out, we'll want make an announcement about how we're positioning it: - We expect this to be...

We're not going to make any changes here. This has some rough edges (using the same types with state and actor proxy invocation) but users that are using Actors today...

I agree that this would be nice to enable, but it's not something we can easily do within the .NET SDK unless we make more options available for choosing the...

I think it be worth starting a design discussion of what it would mean to make the serializer pluggable for actors. https://github.com/dapr/dotnet-sdk/issues/476 As with all things we need to provide...

@beakersoft - this might be a silly question but just in case: ``` public class DeliveryRequest { public double DeliveryLocationLatitude { get; set; } public double DeliveryLocationLongitude { get; set;...

Keeping this issue around as a reminder in case we see it again. Haven't seen it repro again or any issues reported in production.

This happened again here: https://github.com/dapr/dotnet-sdk/runs/2034727454

This is something we can explicitly add to the documentation in a few places. If you are using HTTPS you need to configure Dapr to do the same.