Reuben Bond

Hmm, .g.cs files shouldn't trigger warnings at all, as far as I know. I wonder why this is happening.

xref relevant Discord discussion: https://discord.com/channels/333727978460676096/333727978460676096/1225932166131744778

Adding to what others have said, you can achieve this in Orleans 7.x just as you could in 3.x. It's done a little differently: you would add the relevant assemblies...

1. the partition grain aligns well with Orleans. How have you implemented it? 2. ActivationCountBased placement works based on all activations rather than by type. I think this is generally...

The basic issue is that while the default grain storage serializer is a JSON serializer, the storage provider has no way to know that. What we could do is implement...

Which App Service plan are you using? If you are only using a single host (and you have no external Orleans clients), you could try with `UseLocalhostClustering()`

This _should_ work. One change which might be needed is to set `listenOnAllHostAddresses: true`. I have opened a PR to update docs with full instructions: https://github.com/dotnet/docs/pull/42781/files#diff-b66d9de75a966a6e75cbc3d3608c153dac5340e7d12a2ef6ba6758929e2875b9

You certainly should not inject 'object' into anything use a more specific type. The most common reason for this issue is not having the Microsoft.Orleans.Sdk package installed in all places

I'll close this issue since the original poster had a different issue and the behavior in the Orleans code base is correct: IEnumerable vs non-IEnumerable injection is purely a call...

Should we also add `IPopulator`?