⚡ Update ABP CLI and ABP Suite
dotnet tool update -g Volo.Abp.Studio.Cli --version 0.8.1
abp suite update --version 8.3.0
📗 Blog post
- https://abp.io/blog/announcing-abp-8-3-release-candidate
- https://abp.io/blog/announcing-abp-8-3-stable-release
🔼 Migration guides
- https://abp.io/docs/8.3/release-info/migration-guides/abp-8-3
✏️ Feel free to report any bugs, issues, and problems.
11 Answer(s)
-
0
-
0
This has been around for a while. And still there in abp suite 8.3.0:
-
0
Get this every time clicking on the Save and Generate button (even when it has been just built):
-
0
Hi! We have no 8.3.0 version for Volo.Abp.Studio.Cli. You can view version compatibility from this document: https://abp.io/docs/latest/studio/version-compatibility
We haven't released a version for 8.3.0 packages yet. We will after we finish our controls. For now, if you want to use 8.3.0 version packages for your Studio templates, you can easily upgrade your packages from here:
-
0
This has been around for a while. And still there in abp suite 8.3.0:
Thank you for your feedback, we have an open issue for this problem on the Blazor WebApp UI. We will solve it as soon as possible on the next patches.
-
0
Get this every time clicking on the Save and Generate button (even when it has been just built):
Could you give us specified information about your problem, so we can help you to solve this issue? I did not encounter this situation when I generated entities with Suite. I'm waiting for your details to help you.
-
0
Hi! We have no 8.3.0 version for Volo.Abp.Studio.Cli. You can view version compatibility from this document: https://abp.io/docs/latest/studio/version-compatibility
We haven't released a version for 8.3.0 packages yet. We will after we finish our controls. For now, if you want to use 8.3.0 version packages for your Studio templates, you can easily upgrade your packages from here:
Hi @EngincanV, in your first post the command "dotnet tool update -g Volo.Abp.Studio.Cli --version 8.3.0" is wrong. Version 8.3.0 is for Legacy CLI and not for Abp Studio.
Hi @oyku.erman, When will abp studio support abp 8.3.0? And when https://abp.io/docs/latest to "8.3 (lastest)" ?
Since VoloSoft is pushing to use Abp Studio I expected that with the release of a new version of ABP after 1 or 2 days we would have everything aligned.
I ask you for an extra effort because the use of abp studio in our work workflow should be transparent and today instead it is creating delays due to understanding what has been fixed and what has not.
This will be even more evident with the preview that uses .Net 9
Thank you for your commitment.
-
0
Hi! We have no 8.3.0 version for Volo.Abp.Studio.Cli. You can view version compatibility from this document: https://abp.io/docs/latest/studio/version-compatibility
We haven't released a version for 8.3.0 packages yet. We will after we finish our controls. For now, if you want to use 8.3.0 version packages for your Studio templates, you can easily upgrade your packages from here:
I'm just following instructions at the head of this post:
-
0
Hi! We have no 8.3.0 version for Volo.Abp.Studio.Cli. You can view version compatibility from this document: https://abp.io/docs/latest/studio/version-compatibility
We haven't released a version for 8.3.0 packages yet. We will after we finish our controls. For now, if you want to use 8.3.0 version packages for your Studio templates, you can easily upgrade your packages from here:
I'm just following instructions at the head of this post:
Updated, thanks for the correction. Regards.
-
0
Can't modify the templates of a module created in ABP Suite.
The project was created with ABP Studio and the module was created in ABP Suite then the module was added in ABP Suite and tried to modify the Templates but this exception happens
-
0
Can't modify the templates of a module created in ABP Suite.
The project was created with ABP Studio and the module was created in ABP Suite then the module was added in ABP Suite and tried to modify the Templates but this exception happens
The Volo.Abp.Commercial.SuiteTemplates dll is not added when you create a new module
