Open Closed

Angular: Error handling large amount of Entities / Appservices (approx 2000 App services) #11206

ayoyusuf created


Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • What is your product version? 11.1
  • What is your product type (Angular or MVC)? Angular
  • What is product framework type (.net framework or .net core)? .net Core

We have a large application and my understanding is that ASP.NET ZERO is enterprise ready and hence I am hitting some size based performance limitations that I am getting concerned about. So, need clarification on the advise methodology for resolution.

I have created and Compiled successfully about 2,000 Service in the .net Core and all corresponding dtos. The Swagger is loading and running fine. The Angular NSWAG refresh succeeded.

But on compilation of the Angular I get this Error:

Error: src/shared/service-proxies/service-proxy.module.ts:9:16 - error TS2590: Expression produces a union type that is too complex to represent.

9 providers: [ ~ 10

... 1505 { provide: HTTP_INTERCEPTORS, useClass: AbpHttpInterceptor, multi: true }, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1506 ], ~~~~~

When I reduce the number of Services it compiles fine, but once the services are all their it gives this error. I have tried switching services and it compiles with all the services provided the number is much smaller. So the issue is due to number of services involves.

Is there way around this? (are there other Size related performance issues I should be looking at for?) Has ASP.NET Zero been tested with large Enterprise apps as this is one of several performance snaggs I have hit and now getting very worried. (Earlier raised the issue of several minutes of wait time for the Permission screens to load. Still no solution for that).

1 Answer(s)
  • 0
    musa.demir created
    Support Team

    Hi @ayoyusuf

    It seems like it is typescript side problem. 2000 is a big number and it might be very complex to resolve. See

    Can you check if you can solve the problem by dividing the implementations in your service proxy file into several different files?