Ok. So my assumption was incorrect. I will try to discover and find similarities from all problematic proxies to identify what could make them beahave differently from others. I'm not sure do I have time reserved to make example project now. I will inform this to my product officer.
Hello, I did assume as well that this was same bug but apparently is isn't. Because as you can se I'm working already 8.2.1 version. Try to create this kind of endpoint: [HttpGet] public virtual Task<PagedResultDto<MyDto>> GetListAsync() { return _myAppService.GetListAsync(); } And then generate proxies with this tool of yours like this: abp generate-proxy -t ng -m app --target MyApplication -a default
I found this similar Support ticket. https://abp.io/support/questions/6657/Generation-of-Service-Proxies-for-Angular-not-handling-subclasses-of-PagedResultDtoT-correctly Last answer is not acceptable. At least you need to try fix it. Or say you will at future.
Now something came out https://abp.io/docs/latest/release-info/migration-guides/abp-8-2
My collegue just noticed that change. It was removed when I make these changes https://docs.abp.io/en/commercial/latest/migration-guides/v8_0#added-the-accountadminapplicationmodule-accountadminhttpapimodul Tahnk you.
Bad news. We face this exception still when running at Azure. We updated to 8.1.2. And it seems to work at local machine.
Cannot resolve parameter 'Volo.Abp.Account.ExternalProviders.IAccountExternalProviderAppService accountExternalProviderAppService' of constructor 'Void .ctor(Microsoft.Extensions.Options.IOptionsFactory`1[Microsoft.AspNetCore.Authentication.Google.GoogleOptions], Volo.Abp.Account.ExternalProviders.IAccountExternalProviderAppService, Volo.Abp.Security.Encryption.IStringEncryptionService, Volo.Abp.MultiTenancy.ITenantConfigurationProvider, System.Collections.Generic.IEnumerable`1[Volo.Abp.Account.Public.Web.ExternalProviders.IPostConfigureAccountExternalProviderOptions`1[Microsoft.AspNetCore.Authentication.Google.GoogleOptions]])'.
our packages-lock.json did contain something wrong when it was generated before commercial packages were available. No we got those packages and performance problem is gone. Thank you.
Still no commercial packages. Am I missing something or are they still not yet available.
I noticed that 8.1.2 is published. Should there be commercial nuget packages already available because for some reason nuget install fails?
We cannot git revert to 8.0 because your tool not support to update to spesific version. We decide to put update task on hold untill you release new version. We don't know how to fix that 8.0.5 login page problem so we wait.