- ABP Framework version: v8.3.1
- UI Type: MVC
- Database System: EF Core (SQL Server)
- Tiered (for MVC) or Auth Server Separated (for Angular): yes/no NO
- Exception message and full stack trace:
- Steps to reproduce the issue:
Created a project in ABP Suite v. 8.3.0 project solution. Upgraded abp studio to 0.8.3 Upgraded project to 8.3.1 bits of ABP app. App works. abp suite works. Tried to edit and was prompted to update with message ABP Suite A version inconsistency is detected. Your solution is using ABP v8.3.1 but you have ABP Suite v8.3.0 installed. ... Would you want to auto-install the correct version and continue? CLICKED Yes. Uh oh. Looks like abp suite 8.3.1 installed. Checked tools>change version> and 8.3.1 is in the list. ABP SUITE: It won't launch. When I click Open ABP Suite from the ABP Studio menu, a dialog pops up. Couldn't open ABP Suite. When I click Change Version Dialog: ABP Suite is running now. Please stop it before changing the version. Rebooted PC to clear any locked files and same issue. Ran dotnet tool uninstall -g volo.abp.suite Got this message: Tool 'volo.abp.suite' (version '8.3.1') was successfully uninstalled. Launched ABP Studio. Opened my project. Clicked ABP Suite from Context Menu (right click on solution icon) Prompted to install abp suite. The installer Installed abp suite 8.3.0, not 8.3.1 Now, when opening 8.3.1 project I can open the project. Sooner or later, will get prompted about version inconsistency. All of the imports show up as 8.3.0 All of the .csproj packages show up as 8.3.1 (since I manually updated them).
Any ideas? Thanks in advance.
1 Answer(s)
-
0
Hi, for ABP Studio v0.8.3 you should use ABP v8.3.0 (here is the documentation for version compatibility: https://abp.io/docs/latest/studio/version-compatibility).
If you upgrade your solution to 8.3.1, yes you should also update ABP Suite to 8.3.1 as well. It seems that ABP Studio, it only sees the hardcoded latest ABP version, which is v8.3.0. This is why you could not generate CRUD pages. We have created an internal issue for the problem.
For a quick workaround, you can update your ABP Suite to v8.3.1 and run the
abp suitecommand in a terminal, so the suite would be running in the terminal, and then try to open ABP Suite from the ABP Studio UI and generate CRUD pages.Regards.
