- 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:
- Started the application
- Navigated to the HttpApi.Client folder
- 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)
-
0
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
fileManagementalready 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.
