Hello ABP Support Team,****
We are currently using ABP version 5.4.3 with the MVC UI, and downloaded the source code for all the modules. We are planning to upgrade our application to the latest version of ABP. We have made modifications in several modules (Payment, Account, Identity) and added custom payment gateways and we want to remove most of the module source code.
Before starting the upgrade process, I have a couple of questions:
Upgrade Steps:
Do we need to follow the step-by-step migration process—i.e., upgrading from 5.x to 6.0, then 6.0 to 7.0, then 7.0 to 8.0, and finally to 9.1—or is it possible to upgrade directly from 5.x to 9.1?
Custom Module Changes:
Given our modifications in the Payment, Account, and Identity modules, are there any best practices or tips you would recommend for transferring our custom changes to the new version’s modules?
Any advice or documentation pointers on handling these aspects during the upgrade would be greatly appreciated.
1 Answer(s)
-
0
Hi, here are the answers to your questions:
Do we need to follow the step-by-step migration process—i.e., upgrading from 5.x to 6.0, then 6.0 to 7.0, then 7.0 to 8.0, and finally to 9.1—or is it possible to upgrade directly from 5.x to 9.1?
Yes, we recommend following a step-by-step migration process. This approach helps you upgrade your project more efficiently and minimizes the risk of build errors.
You can refer to our Migration Guides and make the related alignments for each version.
Custom Module Changes:
Given our modifications in the Payment, Account, and Identity modules, are there any best practices or tips you would recommend for transferring our custom changes to the new version’s modules?Once you've customized and overridden a module’s services, we unfortunately cannot offer automation to synchronize those changes during the upgrade. The best approach is to carefully follow our migration guides. These guides highlight the updates made in the related module classes, including modified method signatures and other important changes.
After completing the migration, if you encounter any issues, you can always download the source code of the affected module in the target version to compare and adjust your implementation accordingly.
Any advice or documentation pointers on handling these aspects during the upgrade would be greatly appreciated.
To automatically update ABP packages, you can either use the
abp update --version <version>command or ABP Studio to update your solution from directly from a desktop application.Best Regards.
