What is the best approach to upgrade an old net 3.1 version solution to latest version ? Do we need to do an incremental upgrade ? or we can do direct upgrade ?
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, and please use the search on the homepage.
If you're creating a bug/problem report, please include the followings:
- ABP Framework version: v7.0.3
- UI type: MVC
- DB provider: EF Core
- Tiered (MVC) or Auth Server Separated (Angular): no
- Exception message and stack trace:
- Steps to reproduce the issue:"
5 Answer(s)
-
0
hi
I suggest you create a 7.x template project and compare the code.
https://docs.abp.io/en/abp/latest/Migration-Guides/Index https://docs.abp.io/en/commercial/latest/migration-guides/index
-
0
I have a solution based on ABP 3.1 and now I am trying to upgrade it using the abp update command.
The Update command is throwing an error.
abp update -v 4.0.0 [00:53:24 INF] ABP CLI (https://abp.io) [00:53:24 INF] Version 4.0.2 (Stable) [00:53:26 WRN] ABP CLI has a newer stable version 7.3.0, please update to get the latest features and fixes. [00:53:26 WRN] [00:53:26 WRN] Update Command: [00:53:26 WRN] dotnet tool update -g Volo.Abp.Cli [00:53:26 WRN] [00:55:09 ERR] Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.Cli.ProjectModification.VoloNugetPackagesVersionUpdater.GetLatestVersionFromMyGet(String packageId) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectModification\VoloNugetPackagesVersionUpdater.cs:line 184 at Volo.Abp.Cli.ProjectModification.VoloNugetPackagesVersionUpdater.UpdateSolutionAsync(String solutionPath, Boolean includePreviews, Boolean includeReleaseCandidates, Boolean switchToStable, Boolean checkAll) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\ProjectModification\VoloNugetPackagesVersionUpdater.cs:line 40 at Volo.Abp.Cli.Commands.UpdateCommand.UpdateNugetPackages(CommandLineArgs commandLineArgs, String directory) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\UpdateCommand.cs:line 69 at Volo.Abp.Cli.Commands.UpdateCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\UpdateCommand.cs:line 40 at Volo.Abp.Cli.CliService.RunAsync(String[] args) in D:\ci\Jenkins\workspace\abp-framework-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\CliService.cs:line 59
-
0
hi
MyGet is down now. You can try again after it is back. You can also upgrade packages to the latest manually.
https://myget.org/
For this kind of upgrade across multiple versions, the update command is not enough, and a lot of manual work is required
-
0
Any pointers for the manual upgrade ? or Update command + Manual ?
-
0
Please refer to the migration guide.
https://support.abp.io/QA/Questions/5470#answer-3a0ca1c7-2d24-1455-09df-baf7732a5f44
