dotnet-sdk icon indicating copy to clipboard operation
dotnet-sdk copied to clipboard

Upgrade gRPC to the version 2.43.

Open GFlisch opened this issue 3 years ago • 2 comments

Compatibility with netStandard 2.0 is possible. Change Dapr.Client from .netCore3.1 to netStandard 2.0 and 2.1. Allow Dapr.Client to be used with .NET 4.6.1 and greater!

Description

The current version of Grp.Client was not compatible with netStandard 2.0. This limit the usage of DaprClient to .netCore3.1 and greater. But the latest version of gRPC.Client is able to run on netStandard2.0. Allowing Dapr.Client to run also on .NET 4.6.1 and greater. This is an added value to bring Dapr in combination with MAN Sidekick project.

The Dapr.Client now target frameworks netStandard2.0 and netStandard2.1.

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

No new unit tests were needed and they pass with sucess.

GFlisch avatar Feb 28 '22 08:02 GFlisch

@GFlisch - Thanks for submitting this issue!

Unfortunately, based on current feedback and trends, we don't have any plans to support netstandard2.0/2.1.

Out of curiosity, what is blocking you here?

halspang avatar Feb 28 '22 21:02 halspang

Hi,

We have a lot of legacy app in .Net 4.6.1. We will use the nuget package Man.Dapr.Sidekick to let us integrate our legacy apps with our new ones.

I need homogeneity when communicating with bindings and pubsub. The other scenario to integrate old applications doesn’t interest me.

With a Dapr.Client built for netStandard2.0 I can do this.

Another question. Why do you promote Man.Dapr.Sidekick in your community call if this is not to use it in a write scenario?

Thanks,

GIlles

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows

From: @.> Sent: Monday, February 28, 2022 10:39 PM To: @.> Cc: @.>; @.> Subject: Re: [dapr/dotnet-sdk] Upgrade gRPC to the version 2.43. (PR #844)

@GFlischhttps://github.com/GFlisch - Thanks for submitting this issue!

Unfortunately, based on current feedback and trends, we don't have any plans to support netstandard2.0/2.1.

Out of curiosity, what is blocking you here?

— Reply to this email directly, view it on GitHubhttps://github.com/dapr/dotnet-sdk/pull/844#issuecomment-1054690109, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABNE2KNQDDCEO6LKD55PZPDU5PTPZANCNFSM5PQNPBBQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

GFlisch avatar Feb 28 '22 22:02 GFlisch

I'm going to close this, as we've updated past 2.43 by now and are maintaining our course to not support netstandard2.0/2.1.

halspang avatar Jan 06 '23 22:01 halspang