James Newton-King

> What about when you want to disable capturing but still have access to instance fields? So here is a real world example of where no capturing + shadowing of...

That error is really strange. gRPC requires HTTP/2 to work. Because you're using https, the client and server negotiate that HTTP/2 is supported using HTTPS+ALPN. The error message you're seeing...

This is the change log between 2.43.0 and 2.44.0: https://github.com/grpc/grpc-dotnet/compare/v2.43.0...v2.44.0-pre1 I don't see anything that could introduce this issue.

I think this is the same as https://github.com/grpc/grpc-dotnet/issues/1946

The ideas talked about in https://learn.microsoft.com/en-us/aspnet/core/grpc/versioning?view=aspnetcore-8.0 for versioning gRPC also apply to gRPC JSON transcoding.

Hi. I took a look at your changes. Why did you remove the obsolete attribute you added? Edit: I made some changes and added the obsolete attribute back.

I discovered that Windows Server 2019 has the same partial support as Windows Server 2022. Here is the PR that modifies the validation - https://github.com/grpc/grpc-dotnet/pull/2362

Should this check be a greater than or equals? There shouldn't be anything in-between winserver2022 and win11. ```cs // Windows Server 2022 partially supported if (windowsVersion.Build == WinServer2022BuildVersion) { return...

I think it looks fine. It's difficult to be sure without testing, and that requires lots of OSes.

Hi This is the same problem as https://github.com/grpc/grpc-dotnet/issues/2361. You can read that issue for more details. Adding this code to the start of the client app disables RTT pings fixes...