James Newton-King

> Is there a reason refresh is called from Idle rather than Connecting? The reason is to reduce latency of initial gRPC calls. If load balancing waited until a connection...

@dlosch What do you expect to happen when a resource adds and remove attributes? For example: 1.) Run the app, attribute foo=true, record one log entry 2.) Seq and Aspire...

Sounds like option 3 is the way to go. It will be a non-trivial change: the current design is resources are added once, never change, and referenced directly by telemetry....

Fixed with https://github.com/dotnet/aspire/pull/5526

AuthContext is legacy from the older Grpc.Core implementation. The docs don't talk about it because getting the identity from HttpContext is better. It wouldn't be difficult to change the IsPeerAuthenticated...

You'll need to call protoc manually to generate CS files and then include those generate files. `Grpc.Tools` is based around msbuild and integrates protoc into an msbuild compilation.

gRPC catches and handles the error. gRPC requires the request is ended with a specific trailing header with the status. Why do you want to catch the exception message?

Should investigate whether it is worth providing an option to gRPC server to rethrow exceptions.

I integrated gRPC HTTP API endpoints with Swashbuckle using the endpoint routing API here - https://github.com/aspnet/AspLabs/tree/master/src/GrpcHttpApi/src/Microsoft.AspNetCore.Grpc.Swagger The most interesting file: https://github.com/aspnet/AspLabs/blob/master/src/GrpcHttpApi/src/Microsoft.AspNetCore.Grpc.Swagger/Internal/GrpcHttpApiDescriptionProvider.cs A little hacky, but it works.

With Blazor WASM, it's up to the browser to decide what protocol to use when making HTTP requests. It can't be controlled from .NET.