We are going to upgrading ABP 8 to ABP 10 (Micro Services template)
I noticed that since ABP9, each MicroService project layout is simplified,
Now it becomes
But I feel like for a system already go lives for years, It is safer to continue using legacy ABP Cli doing the upgrade so that the projects layout would not change significantly.
ABP would keep upgrading legacy ABP cli, right? Any suggestion?
1 Answer(s)
-
0
You don’t need (and shouldn’t try) to “upgrade by re-templating” your existing microservice solution to the new simplified layout. For an already-live system, the safest approach is to keep your current solution/project structure and upgrade by updating ABP packages & applying the official migration guides. ABP’s upgrades are not meant to force you to adopt the latest template folder layout.
About “legacy CLI” / “new CLI”:
- ABP has introduced a newer generation CLI (see https://abp.io/new-cli) and templates may evolve (including microservice structure simplifications).
- Regardless of template changes, your existing solution can remain as-is; the runtime/framework packages are what matter for upgrading.
Practical suggestion for ABP 8 → ABP 10 (microservices template):
- Upgrade incrementally: 8 → 9 → 10 (don’t jump in one step), applying migration changes at each major version.
- Use ABP’s upgrade tooling to switch package versions rather than recreating the solution:
- Use ABP CLI commands as documented in https://abp.io/docs/latest/cli (e.g., switching to stable/target versions where applicable for your workflow).
- Only adopt the new simplified service layout if you explicitly choose to refactor later; treat it as an optional modernization, not a requirement for ABP 10.
ABP Studio/CLI versioning note (so you don’t get surprised by template versions):
- ABP Studio CLI uses a version mapping table (https://abp.io/docs/latest/studio/version-mapping). This can affect which template version is used when creating new solutions, but it doesn’t require restructuring existing ones.
If your goal is “maximum safety”, keep the legacy project layout and focus strictly on package/migration-guide upgrades; refactor structure only as a separate, controlled initiative later.
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.
