grpc-dotnet
grpc-dotnet copied to clipboard
grpc
Add version conditions for Microsoft.Extensions.Http and Microsoft.Extensions.Logging.Abstractions
This merge request adds some conditions in Grpc.Net.Client.csproj and Grpc.Net.ClientFactory.csproj. Actually, this merge request solves this problem.
Thank you in advance.
- :x: The commit (b0dd1a7b9ed0dbb25a031859ff1ef96f248faa0f) is missing the User's ID, preventing the EasyCLA check. Consult GitHub Help to resolve.For further assistance with EasyCLA, please submit a support request ticket.
![linux-foundation-easycla[bot] avatar](https://avatars.githubusercontent.com/in/17893?v=4 "Published by a pub.dev verified publisher"){kind=small}
What does this fix? The older version is forward compatible, and a .NET 6 app can specify to use version 6 of that Microsoft.Extensions library if it wants.
What does this fix? The older version is forward compatible, and a .NET 6 app can specify to use version 6 of that Microsoft.Extensions library if it wants.
Yes, you told me this before, but not everyone knows this. They just install without attention, by the way with this merge request we don't need to install those packages explicitly.
Ok. Usually referencing the lowest version is recommended. However, there are some advantages of bringing in a new version.
Let me talk with some other .NET people. I will see what the general approach is here.
https://github.com/grpc/grpc-dotnet/pull/2021 updates the dependencies to .NET 6