[grpc-io] Re: Updates on gRPC C# (Grpc.Core) support

['Jan Tattermusch' via grpc.io]

Hello Everyone,

Please see the latest update on Grpc.Core deprecation 
.

On Tuesday, July 4, 2023 at 5:02:10 PM UTC+2 Jan Tattermusch wrote:

> FYI added some updates about the current status of Grpc.Core here: 
> https://github.com/grpc/grpc/issues/32719#issuecomment-1620399357
> On Wednesday, June 7, 2023 at 11:33:53 AM UTC+2 Zaphod Stardust wrote:
>
>> @Jan Tattermusch:
>> I understand  that now the "maintenance mode" of Grpc.Core is over.
>> That means Grpc.Core is now officially deprecated, correct?
>>
>> What are the rules / support policies that apply now?
>> -> No fixes (even for security) any more (besides contributed by open 
>> source community)?
>>
>> Thanks for clarifying!
>>
>> Jan Tattermusch schrieb am Dienstag, 3. Mai 2022 um 11:25:07 UTC+2:
>>
>>> Hello gRPC C# Users!
>>>
>>> In May 2021 we announced  
>>> that Grpc.Core (the original C# implementation of gRPC) became "maintenance 
>>> only" and that grpc-dotnet will be the recommended implementation going 
>>> forward. We also announced that Grpc.Core will become deprecated in the 
>>> future.
>>>
>>> While all the above is still the plan, we are making some adjustments 
>>> based on the user feedback we received. We also wanted to publish more 
>>> details about the plan and its technical execution. All the important 
>>> updates are summarized in the following sections of this announcement.
>>> Grpc.Core maintenance period will be extended by 1 more year (until May 
>>> 2023)
>>>
>>> Originally we planned to deprecate the Grpc.Core implementation in May 
>>> 2022, but the feedback we received from users has indicated that extending 
>>> the maintenance period would make sense. Without going too much into the 
>>> details, the main points of the feedback can be summarized as:
>>>
>>>- 
>>>
>>>The main blocker for deprecating Grpc.Core is the lack of support of 
>>>the legacy .NET Framework in grpc-dotnet. The desire to migrate off the 
>>>legacy .NET framework is often there, but migrating workloads from .NET 
>>>Framework to .NET Core / .NET 6 simply takes time and effort.
>>>- 
>>>
>>>Grpc.Core is a very important technology for enabling migration off 
>>>.NET Framework (since it enables piece-by-piece migration by 
>>>interconnecting components on newer .NET platforms with components that 
>>>remain on .NET Framework), so supporting it for a little longer can 
>>>(somewhat paradoxically) help users migrate off it faster.
>>>
>>>
>>> As a result, we are delaying the deprecation of Grpc.Core until May 2023 
>>> (1 year from now, and 2 years after the original announcement). Until 
>>> then, Grpc.Core will remain to be supported in the "maintenance mode", as 
>>> described below.
>>>
>>> Since the plan to deprecate Grpc.Core has been now publicly known for a 
>>> while and since the main reason we are extending the maintenance period is 
>>> to deal with the issues related to the legacy .NET Framework (and migration 
>>> off it), we also want to clarify what exactly will be covered by the 
>>> "Grpc.Core maintenance" going forward:
>>>
>>>- 
>>>
>>>The main goal of keeping Grpc.Core alive is to maintain the ability 
>>>to run gRPC C# clients and servers on the legacy .NET Framework on 
>>> Windows. 
>>>This will be taken into account when considering issues / fixes.
>>>- 
>>>
>>>We will only provide critical and security fixes going forward. This 
>>>is to minimize the maintenance costs and reflects the fact that 
>>> grpc-dotnet 
>>>is the recommended implementation to use.
>>>- 
>>>
>>>There will be no new features for Grpc.Core. Note that since 
>>>Grpc.Core is moving to a maintenance branch (see section below), there 
>>> will 
>>>also be no new features coming from the native C-core layer.
>>>- 
>>>
>>>There will be no new platform support and portability work. The 
>>>focus will be on continuing support for the legacy .NET Framework on 
>>>Windows (where there is no alternative implementation to use) and the 
>>> list 
>>>of supported platforms will not be expanded (e.g. we will not work 
>>> towards 
>>>better support for Unity, Xamarin, Alpine Linux etc.). We will likely 
>>> drop 
>>>support for platforms that have been so far considered as "experimental" 
>>>  
>>>(e.g. Unity and Xamarin), since they are also hard to test and maintain.
>>>- 
>>>
>>>Work to support new .NET versions (.NET6, NET 7, …) will be kept to 
>>>a minimum (or not done at all) since those .NET versions fully support 
>>>grpc-dotnet.
>>>- 
>>>
>>>No more performance work: Since the main purpose of Grpc.Core is to 
>>>maintain interoperability with legacy .NET framework, there will be less 
>>>focus on performance. We do not expect any significant performance 
>>> drops, 
>>

[grpc-io] Re: No replacement for grpc.core for NET Framework on Windows 10

['Jan Tattermusch' via grpc.io]

Please see the latest update on Grpc.Core deprecation 
.

On Monday, June 26, 2023 at 4:17:37 PM UTC+2 Jan Tattermusch wrote:

> Hi,
>
> I understand that deprecating Grpc.Core will come with limitations for 
> some users, but unfortunately it isn't always possible to make everyone 
> happy. The article you linked tried to explain what lead us to the decision 
> to eventually deprecate Grpc.Core in favor of grpc-dotnet and maintaining 
> Grpc.Core takes effort (that could otherwise be spent on more 
> forward-looking improvements to gRPC in .NET) and we believe that those 
> arguments still apply.
>
> TBH, this isn't really about having Windows 10 or newer, it's more about 
> using the "legacy" .NET Framework or using the more modern .NET Core. 
> grpc-dotnet has a full feature support on .NET Core (followed by .NET 
> 5,6,..) and a much more limited feature support on the legacy .NET 
> Framework and the version of Windows doesn't really change much in this 
> picture.
> While it is clear that not everyone have migrated to .NET Core by now 
> (even though it existed for many years now and it's been heavily 
> recommended by Microsoft), there is no clear deprecation date for the 
> legacy .NET Framework in the foreseeable future (some say it will live 
> "forever") and we have to draw a line somewhere. The blogpost you linked 
> gave folks 2+ years notice to prepare for Grpc.Core being
> deprecated (and we did our best to support Grpc.Core during this 
> maintenance period) and we cannot support it forever (we already extended 
> the support period by one year in 2022).
>
> Hope this makes sense
> On Thursday, January 12, 2023 at 11:57:41 AM UTC+1 Chris Husslack wrote:
>
>> Hi All.
>>
>> The grpc.core library will soon be obsolete as mentioned here 
>> . For NET Framework and NET 
>> Core the replacement for clients is grpc.net.client. Unfortunately for the 
>> NET Framework there are major limitations as listed here 
>> .
>>  
>> This means that it is not possible to consume grpc services which only 
>> support HTTP/2 requests on Windows 10 using NET Framework. This is a major 
>> limitation. Windows 10 is still widely used. The migration from NET 
>> Framework to NET Core takes also time with a large code base. While Google 
>> stops the support for the NET ecosystem Microsoft does not pick it up 
>> completely. 
>>
>> May I ask the humble question to extend the support for grpc.core until 
>> Windows 10 is EOL 
>> 
>> ?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/61c3dbed-b1b7-43f6-9552-16b074c9335bn%40googlegroups.com.

[grpc-io] Updates on gRPC C# (Grpc.Core) support [October 2023]

['Jan Tattermusch' via grpc.io]

Hello gRPC C# Users!

In May 2022 we extended 
the maintenance of Grpc.Core, updating the original announcement
 from 2021. We have yet another
update for you today - while we still plan to deprecate Grpc.Core in the
future, we decided that 2023 is not the right time to do it.

Here are the main reasons for delaying the Grpc.Core deprecation beyond the
originally planned date of May 2023:

   -

   Grpc.Net.Client  does work on the legacy .NET
   Framework, but it requires a recent-enough version of Windows. The rollout
   of the necessary patches to Windows (specifically to their WinHttpHandler
   component) has been slower than anticipated, so some windows versions where
   Grpc.Net.Client  over WinHttpHandler doesn't
   work (e.g. Windows 10 and Windows Server 2019) are supported by Microsoft
   and are still relatively widely used.
   -

   We received feedback that Grpc.Core is very useful when migrating
   systems from .NET Framework to the more modern .NET 6+, so keeping
   Grpc.Core available for a little longer would make it easier for users to
   move towards platforms where grpc-dotnet is better supported.
   -

   Google API client libraries still use Grpc.Core when running on some
   legacy systems (namely on .NET Framework)



As a result, we are delaying Grpc.Core deprecation until further notice,
but at least 1 year from now (i.e. until at least October 2024). Until
then, Grpc.Core will remain to be supported in the "maintenance mode":

   -

   The team will limit any interventions regarding Grpc.Core to a bare
   minimum. This is to decrease maintenance costs and reduce the risk of
   breaking something. This means we will only make critical and security
   fixes for Grpc.Core going forward.
   -

   Grpc.Core is expected to stay at current maintenance branch (v1.46.x
    on the grpc/grpc repository)
   as long as that's technically feasible
   -

   The actual deprecation date for Grpc.Core is currently unknown and will
   be provided via an update in the future (consider Grpc.Core as in
   maintenance mode until then). The deprecation date is likely going to be
   aligned with end of support of one of the legacy platforms (e.g. Windows 10
   goes EOL), but this is something that will be determined later, based on
   technical circumstances.
   -

   Note that as soon as Grpc.Net.Client  on .NET
   Framework works on a given platform, we will consider that as the platform
   being sufficiently well supported to not require Grpc.Core. Note that this
   means that after the Grpc.Core deprecation happens, there can be legacy
   platforms where only the gRPC client will be supported (and not the gRPC
   server).


Feel free to reply to this announcement with follow up questions and
requests for clarification. For major issues connected to the
migration/deprecation plan, you can file an issue on github as usual.

On behalf of the gRPC team,

Jan

-- 

Jan Tattermusch

Software Engineer


Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise erhalten
haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter,
löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen,
dass die E-Mail an die falsche Person gesendet wurde.



This e-mail is confidential. If you received this communication by mistake,
please don't forward it to anyone else, please erase all copies and
attachments, and please let me know that it has gone to the wrong person.

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CACF4M0TPoQeYAwXCoXtxjm856hw4vZ17T_%3D5SKR4M6veLvxWxA%40mail.gmail.com.


smime.p7s
Description: S/MIME Cryptographic Signature

[grpc-io] gRFC A61: IPv4 and IPv6 Dualstack Backend Support

['Mark D. Roth' via grpc.io]

I have published a gRFC for dualstack backend support:

https://github.com/grpc/proposal/pull/356

Comments welcome!

-- 
Mark D. Roth 
Software Engineer
Google, Inc.

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAJgPXp6ueoog18qFJPCL1kxT_nkL0ro%2BtgsCMBxzSk%3D8PpHd%3Dg%40mail.gmail.com.

[grpc-io] Re: Trying to build an embedded Linux using Unity and grpc.

['Jan Tattermusch' via grpc.io]

Hello, please note that gRPC C#'s support for Unity is experimental-only. 
Therefore it's not guaranteed to work (and we also don't provide support if 
it breaks). My only advice would be to search the web for folks that have 
run into similar problems as you did and hopefully that will help you with 
the problem you're seeing.

On Monday, August 28, 2023 at 12:14:01 PM UTC+2 강미진 wrote:

>  Hello,
>
> I saw an article that gRPC supports ARM64 Linux.
>
> https://grpc.io/blog/grpc-on-arm64/
>
>
> So, I tried to build an arm64 in Unity, but I get this error and I can't 
> build.
>
>
>
>
> The error "*undefined symbol:grpcsharp_init"  *appears, 
> Can't I use it in unity?
>
> I used the zip file provided by this site.
> https://packages.grpc.io/
> grpc_unity_package.2.47.0-dev202204190851.zip 
> 
>
>
> This is my first time using Unity and grpc, so I'm not sure what else I 
> should do.
>
> Can I get a little help?
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/f3cda68b-9cd0-490a-8170-c25061905ba6n%40googlegroups.com.