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
Few days ago I found migration guide to 8.2 but yesterday and today links are not working anymore. Here are two links https://abp.io/blog/announcing-abp-8-2-release-candidate Which are going to https://docs.abp.io/en/abp/8.2/Migration-Guides/Abp-8_2 and https://docs.abp.io/en/commercial/8.2/migration-guides/v8_2 and they are nto working anymore. Also migration guide for 8.2 is missing from here too https://abp.io/docs/latest/release-info/migration-guides
I assume that FlagIcon needs to be removed from several places, IdentitySession needs to be added to DbContext and then berhaps we need to add these packages to HttpApi.Host project (I found some problem for others if they are not added) <PackageReference Include="Microsoft.IdentityModel.Protocols.OpenIdConnect" Version="7.5.1" /> <PackageReference Include="Microsoft.IdentityModel.Tokens" Version="7.5.1" /> <PackageReference Include="Microsoft.IdentityModel.JsonWebTokens" Version="7.5.1" />
When I generate proxies for my angular application files are broken because of broken imports. I have noticed that it might be related to PagedResultDto<T> So make endpoint which returns object which extends PagedResultDto<MyObject> then generate proxies like this: abp generate-proxy -t ng -m app --target MyProject -a default Then you noticed that in model file there is extra import for MyObject even when MyObject is declared in same file. Here is one example of our proxy model:
import type { VendorDto } from '../scm/master-data-management/vendors/models';
import type { PagedResultDto } from '@abp/ng.core';
import type { CalculatedOrderProposalSummaryItemDto } from './models';
import type { OrderProposalFocusBarValuesDto } from '../order-proposal-focus-bar-values/models';
export interface CalculatedOrderProposalSummaryItemDto {
vendor: VendorDto;
vendorGroupName?: string;
}
export interface PagedOrderProposalSummaryItemResultDto extends PagedResultDto<CalculatedOrderProposalSummaryItemDto> {
focusBarValues: OrderProposalFocusBarValuesDto;
calculationDate?: string;
}
So here CalculatedOrderProposalSummaryItemDto is imported even that it is declared in same file. So fix would be don't import interface when it is declared in same file.
This started to happend after we upgraded from abp 7 to abp 8.
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.