Base solution for your next web application
Open Closed

Service Proxy Too Large #11662


User avatar
0
mahendra created

Hello Expert,

When we use refresh.bat in angular application, it creates a single proxy file which is huge and then further this file increases the size of the main bundle and hence increases the initial load time of the application.

How can we split the one proxy.ts file into multiple files.

While searching on internet, I can see that ABP.io provides a command "abp generate-proxy -t ng" that creates seperate file for every controller and app service. Do we have similar approach for ASPDotNetBoilerplate.

Please advise. Regards, Mahendra


8 Answer(s)
  • User Avatar
    0
    mahendra created

    Hi there,

    Any update on this please....

    Regards, Mahendra

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @mahendra

    We are using NSWAG and it doesn't provide such a feature.

  • User Avatar
    0
    mahendra created

    Is there any workaround?

  • User Avatar
    0
    m.aliozkaya created
    Support Team

    Hi @mahendra,

    We don't have a work about on this. We may add it to our roadmap in the future.

  • User Avatar
    0
    mahendra created

    Is this available with ABP.io Framework?

    Regards, Mahendra

  • User Avatar
    0
    m.aliozkaya created
    Support Team

    Hi @mahendra

    Yes, it's available with ABP Framework. You can look at this article.

    https://docs.abp.io/en/abp/latest/UI/Angular/Service-Proxies

  • User Avatar
    0
    mahendra created

    Hi there,

    Can't we use this in ASPNetZero project based on ASPNetBoilerplate framework?

    Our problem is when we do a prod build of angular project, the service-proxies.ts (which itself is huge) is always gets included in main js and it hapmers the initial load time of the application.

    Regards, Mahendra

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @mahendra

    Unfortunately, you can't use ABP.IO's service proxy generation with AspNet Zero at the moment. I have created an issue to investigate options to solve this issue, please follow https://github.com/aspnetzero/aspnet-zero-core/issues/4955