Hi,
I am unable to create proxy and angular components for newly created entities via ABP suite. This is a completely new module under one host application and another module under the same host application, we do not see the these issues.
Appreciate for the quick response.
Please let me know if any logs required to analyze it.
Check the docs before asking a question: https://abp.io/docs/latest Check the samples to see the basic tasks: https://abp.io/docs/latest/samples The exact solution to your question may have been answered before, and please first use the search on the homepage.
Provide us with the following info:
🧐 Hint: If you are using the ABP Studio, you can see all the information about your solution from the configuration window, which opens when you right-click on the solution and click on the Solution Configuration button.
- Exception message and full stack trace:
- Steps to reproduce the issue:
4 Answer(s)
-
0
- Solution Here is a concise checklist to reliably generate both Angular service proxies and ABP Suite Angular CRUD components for newly created entities in a new module:
- Verify backend is running and exposes API definitions
- Start HttpApi.Host with dotnet run (not IIS Express) so the API definition endpoint is reachable.
- Browse to https://localhost:<port>/api/abp/api-definition?includeTypes=true and ensure it returns JSON. Proxies are generated from this endpoint.
- Generate Angular service proxies correctly
- Open a terminal at the Angular app root and run:
- abp generate-proxy -t ng
- If you have multiple remote services or modular solutions, specify:
- abp generate-proxy -t ng --module app --api-name Default
- If prompted by the schematics:
- Backend module name: app (unless you use a custom remote service name)
- Backend api name (remoteServiceName): default (or your remote service name)
- Source Angular project: the project name in angular.json that contains environment.ts (often your defaultProject)
- Target Angular project: the same project name where you want proxies generated
- Open a terminal at the Angular app root and run:
- Ensure Angular project configuration is compatible
- In src/environments/environment.ts:
- apis.default.url points to the running backend
- apis.default.rootNamespace matches your .NET root namespace (e.g., Acme.BookStore)
- In tsconfig.base.json, add:
- "paths": { "@proxy": ["src/app/proxy/index.ts"], "@proxy/": ["src/app/proxy/"] }
- In src/environments/environment.ts:
- Common blockers and fixes
- Multiple Angular modules match during Suite generation
- If ABP Suite fails with “More than one module matches…”, ensure there is a single intended .module.ts under the target folder or configure Suite/schematics to use a specific module. Alternatively, run generation with a module explicitly, or clean up duplicate .module.ts files.
- Visual Studio hosting limitation
- Run backend with dotnet run to avoid known VS hosting issues for the proxy generator.
- CLI and schematics version
- Update ABP CLI to the latest stable: dotnet tool update -g Volo.Abp.Cli
- Ensure @abp/ng.schematics exists in the Angular devDependencies.
- Module not appearing in Suite
- Ensure your new module’s HttpApi and HttpApi.Host expose endpoints and the module is added to the host. If you use a separate HttpApi host per module, point the Angular environment apis entry to that host and use --api-name appropriately.
- After adding new entities/methods
- Rebuild and run the backend, then re-run abp generate-proxy so the new endpoints are reflected.
- Multiple Angular modules match during Suite generation
- Re-generate ABP Suite Angular CRUD pages
- Open ABP Suite, select the entity, and generate Angular UI.
- If the Angular schematic errors about multiple modules, specify the Angular module to import into or ensure only one module matches in the target directory, then re-run.
- Sources
- https://abp.io/docs/latest/framework/ui/angular/service-proxies
- https://abp.io/docs/latest/samples
- https://abp.io/docs/latest
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
Hello,
Could you please specify the ABP version that you have been using? That would also be the best if you could share the suite logs regarding the error.
Thank you for your cooperation.
-
0
In the meantime, please let me know how to get the suite logs and how do we regenerate these logs.
-
0
The logs can be found in
%UserProfile%\.abp\suite\logsfor windows machines and~/.abp/suite/logsfor unix systems.
