- Template: microservice
- Created ABP Studio Version: 2.2.1
- Current ABP Studio Version: 2.2.1
- Multi-Tenancy: Yes
- UI Framework: angular
- Theme: leptonx
- Theme Style: system
- Theme Menu Placement: side
- Database Provider: ef
- Database Management System: sqlserver
- Mobile Framework: none
- Public Website: No
- Social Login: Yes
- Include Tests: Yes
- Dynamic Localization: Yes
- Kubernetes Configuration: Yes
- Grafana Dashboard: Yes
- Use Local References: No
- Aspire: Yes
- Optional Modules:
- GDPR
- FileManagement
- TextTemplateManagement
- AuditLogging
- Chat
- OpenIddictAdmin
- Selected Languages: Romanian (Romania), Russian
- Default Language: Romanian (Romania)
- Create Command: abp new AbpSolution6 -t microservice --ui-framework angular --database-provider ef --database-management-system sqlserver --theme leptonx --skip-migration --skip-migrator --without-cms-kit --aspire --dont-run-install-libs --dont-run-bundling -no-language-management -chat -file-management
Hi,
I've noticed that the abp suite version 10.1.0 fails when crearting new enity. And specifically I presume that happends when it tries to generate the migration for the new entity. Any ideas?
1 Answer(s)
-
0
ABP Suite/Studio does not support UI code generation for the microservice template (Angular UI). In microservice solutions, Suite can generate code on the services, but UI code generation is not supported. If you are trying to generate the Angular UI together with the entity, the generation can fail during the process (often surfacing around migration/object-mapping steps).
- Workaround: generate only the backend (service side) and handle UI manually (or generate UI in a different supported template).
If the failure is happening at the migration step, apply migrations manually instead of relying on Suite’s “add migration / update database” step:
- Create the entity code (backend) without auto-migration (disable “Add Migration/Update Database” if that option is shown).
- In the relevant
*.EntityFrameworkCoreproject for the service, run EF Core migrations manually:
dotnet ef migrations add Added_MyEntity --context <YourDbContextName> dotnet ef database update --context <YourDbContextName>- For ABP 10.1, note that there are framework/module changes that explicitly require creating new EF Core migrations after upgrading (Identity PRO password history/passkey entities, etc.). So if your solution has been upgraded/created around 10.1 and migrations are out of sync, generation/migration steps can also fail until you add/apply the required migrations.
- Ensure you’ve applied the ABP 10.1 migration requirements (especially if you upgraded the solution/packages):
- Add & apply the required EF Core migrations after moving to ABP 10.x/10.1 as described in the migration guides below.
Links (verified):
- https://abp.io/docs/10.1/studio/working-with-suite
- https://abp.io/docs/10.1/release-info/migration-guides/abp-10-1
- https://abp.io/docs/10.1/release-info/migration-guides/abp-10-0
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.
