Hi Zied, Thank you for keeping me updated! But, as I said, I rewrote the code to use the async versions and continue with these sources.
Cheers, Zweitze. On Thursday, March 23, 2023 at 2:59:09 PM UTC+1 Zied Chaari wrote: > Hey Zweitze, > > I think they have fixed the issue. #488 > <https://github.com/googleads/google-ads-dotnet/issues/488> > I have tried the new library and it's working. > > On Monday, March 20, 2023 at 1:46:37 PM UTC Zweitze wrote: > >> Hello Forum Advisor, >> >> On Thursday, March 16, 2023 at 7:20:04 PM UTC+1 Google Ads API Forum >> Advisor wrote: >> >> Hi Zweitze, >> >> Thank you for coming back to us. I hope you are doing well today. >> >> Moving forward to your concern, upon checking there is a related issue >> titled *“**Document that programs may hang after upgrading to 14.0.0+ >> #488* <https://github.com/googleads/google-ads-dotnet/issues/488>*”* created >> on github issue (googleads/google-ads-dotnet) which has a latest response. >> Could you please try if this will work on your end? >> >> GoogleAdsConfig config = new GoogleAdsConfig(); >> config.UseGrpcCore = true; >> GoogleAdsClient client = new GoogleAdsClient(config); >> >> In addition, please see *Supported Frameworks:* >> >> >> - .NET Framework 4.7.2+ (net472) >> - .NET Standard 2.1 (netstandard2.1) >> - .NET 5.0 (net5.0) >> - .NET Core 3.1 (netcoreapp3.1) >> >> >> The library doesn't have an explicit build target for .NET 6.0 (net6.0) >> yet. However, you can use the library with a binary built for .NET 6.0, >> since netstandard2.1 is compatible with .NET 6.0. >> >> Have a great day. >> >> >> Please check that issue that you referenced. >> Check who reported that particular issue. Yes, that was me. >> >> And the issue is about documentation. And yes, this breaking change is >> still not documented anywhere, except in issues #480 >> <https://github.com/googleads/google-ads-dotnet/issues/480> and #488 >> <https://github.com/googleads/google-ads-dotnet/issues/488> >> It took me four weeks (!) to get the projects in my solution working with >> async calls, and I think it should be fair to warn others about this >> change. That is the reason I point others to the issues - when I was facing >> the problem it took me two days to find the explanation, the then well- >> buried issue #480. >> >> So it's working for me - after making everything async, as was suggested >> in #480 <https://github.com/googleads/google-ads-dotnet/issues/480> >> About the suggestion you make here - I already checked that long ago. >> When instantiating GoogleAdsConfig, it's member UseGrpcCore is already set >> to true. Setting it to true once more does not help. >> >> About your question on the platform: see the issue I created. >> >> >> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "Google Ads API and AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/3e02cf1c-1ebc-4648-ba28-d84cc5150956n%40googlegroups.com.
