Ends in:
2 DAYS
5 HRS
10 MIN
41 SEC
Ends in:
2 D
5 H
10 M
41 S
Open Closed

Dynamic JavaScript API Client Proxies and the Web Project #2452


User avatar
0
AlderCove created
  • ABP Framework version: v5.1.1
  • UI type: MVC
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes

Please help me to understand the Dynamic JavaScript API Client Proxies, the architecture a little better and that I am taking the correct steps for accessing the proxies from the Web application.

In order to access module proxy scripts from the Web project, I did the following:

  1. Started the application
  2. Navigated to the HttpApi.Client folder
  3. Generate the client proxies (abp generate-proxy -t csharp -m fileManagement -url https://localhost:44308/)

I notice though that all of these proxy scripts are available from the HttpApi (https://localhost:44308/Abp/ServiceProxyScript) project and wonder why the Web project doesn't utilize the HttpApi scripts directly?

I also noticed that some of the framework modules are available already in the HttpApi.Client (abp, cms-kit and cms-kit-pro module), while some of the other ones I am using are not.

Thanks - appreciate the help.


1 Answer(s)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    I also noticed that some of the framework modules are available already in the HttpApi.Client (abp, cms-kit and cms-kit-pro module), while some of the other ones I am using are not.

    hi

    The fileManagement already has the static proxy cs and js. You don't need to add it again. You only need to generate the proxy in your module.

Made with ❤️ on ABP v9.1.0-preview. Updated on December 02, 2024, 12:35