You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m not sure if this is a bug with this project, or WCF, but this somehow breaks the reflection for user.GetService<CreativeService>(); resulting in something like this:
MissingMethodException: Constructor on type 'Google.Api.Ads.AdManager.v202308.CreativeService' not found.
4.10.3 does not have that issue. I didn’t actually need that reference any longer (this was a service that started life as a .NET Framework 4 WCF Service), but as I just spent 2 hours debugging this weird issue, I thought it should at least be mentioned somewhere.
The text was updated successfully, but these errors were encountered:
On Tue, Oct 17, 2023, 1:49 AM Christoph Wagner ***@***.***> wrote:
I’m not sure if this is a bug with this project, or WCF, but this somehow
breaks the reflection for user.GetService<CreativeService>(); resulting
in something like this:
MissingMethodException: Constructor on type 'Google.Api.Ads.AdManager.v202308.CreativeService' not found.
4.10.3 does not have that issue. I didn’t actually need that reference any
longer (this was a service that started life as a .NET Framework 4 WCF
Service), but as I just spent 2 hours debugging this weird issue, I thought
it should at least be mentioned somewhere.
—
Reply to this email directly, view it on GitHub
<#252>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCOJCDYKHSWDSHH6ML3TH3X7YL6DAVCNFSM6AAAAAA6DH3XQGVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2DMNJZGQ3DMMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
I’m not sure if this is a bug with this project, or WCF, but this somehow breaks the reflection for
user.GetService<CreativeService>();
resulting in something like this:4.10.3 does not have that issue. I didn’t actually need that reference any longer (this was a service that started life as a .NET Framework 4 WCF Service), but as I just spent 2 hours debugging this weird issue, I thought it should at least be mentioned somewhere.
The text was updated successfully, but these errors were encountered: