- ABP Framework version: v9.0.0
- UI Type: Angular / MVC / Blazor WASM / Blazor Server
- Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..) / MongoDB
- Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
- Exception message and full stack trace:
- Steps to reproduce the issue:
When i try to create .net core 8 project by switch the version in abp studio the project still come out as .net 9. most of the internet still dont support .net 9 so i want to switch back to 8. how do i do that?
13 Answer(s)
-
0
I have this problem too
-
0
Is this possible?
-
0
hi
Can you change all
net9.0target tonet8.0incsprojfiles?You can also use old CLI to create a new 8.x project and then develop it in Studio.
https://abp.io/docs/latest/cli/differences-between-old-and-new-cli
-
0
hi
Can you change all
net9.0target tonet8.0incsprojfiles?You can also use old CLI to create a new 8.x project and then develop it in Studio.
https://abp.io/docs/latest/cli/differences-between-old-and-new-cli
In the linked doc it says: With v8.2+, ABP introduces a new templating system, which is fully compatible with the ABP Studio. So, if I choose the template Ex: 8.3.2 the project must be target net8 and I must not modify it by hand. In my opinion it is an error of Abp studio that does not manage this parameter correctly.
In addition, Volosoft had said that it would always maintain the version in Microsoft LTS support so I expect that it can continue to create projects and develop with abp studio and .Net8. As well as I expect that the fixes will also be made in the .Net8 templates (abp 8.x) and not only in the .net9 templates (abp 9.x).
Thanks
-
0
hi roberto.fiocchi
We will fix this in Studio.
-
0
Hello there,
In the linked doc it says: With v8.2+, ABP introduces a new templating system, which is fully compatible with the ABP Studio. So, if I choose the template Ex: 8.3.2 the project must be target net8 and I must not modify it by hand. In my opinion it is an error of Abp studio that does not manage this parameter correctly.
What you say is correct, but I see that there are a few misunderstandings. First of all, there is no obstacle to generate a template with version
8.3.2. See here. You can open the template you generated in the latest version of ABP Studio and use all its features, there is no limitation or problem with that. You cannot create a project targeting.NET 8only with the latest version of ABP Studio. As Maliming said, we have an issue on this subject but unfortunately, it is not a prioritized.In addition, Volosoft had said that it would always maintain the version in Microsoft LTS support so I expect that it can continue to create projects and develop with abp studio and .Net8.
With the latest version of ABP Studio, you cannot generate a project targeting .NET 8, you can however continue to develop it. If you want to create a project targeting .NET 8, you can refer here.
As well as I expect that the fixes will also be made in the .Net8 templates (abp 8.x) and not only in the .net9 templates (abp 9.x).
Yes, we pay as much attention to this as we can. You can open an issue if you have a problem with this.
-
0
Thanks for the reply, but can you confirm that Abp Studio (desktop app) and Abp Studio Cli (console app) use the same templates to create the solution?
-
0
Thanks for the reply, but can you confirm that Abp Studio (desktop app) and Abp Studio Cli (console app) use the same templates to create the solution?
I can verify that it will generate the same template if they are both in the same version. This means that you can switch between the versions of Studio's CLI (Volo.Abp.Studio.Cli) application and generate the project to be rendered with the new template engine in the ABP version you want. You can look here for version mapping.
-
0
Ok, can you do that for me?
Thanks
-
0
You can find the relevant terminal commands below:
// Uninstall CLI dotnet tool uninstall --global Volo.Abp.Studio.Cli // Install CLI with 0.9.7 version. This version generates templates with 8.3.3 of ABP version dotnet tool install --global Volo.Abp.Cli --version 0.9.7 // Template generation. You can change the parameters to fit you. abp new Acme.BookStore --csf // Necessary codes to switch back to the latest version of the CLI dotnet tool uninstall --global Volo.Abp.Studio.Cli dotnet tool install --global Volo.Abp.Cli -
0
Volo.Abp.Cli is Legacy Cli and in theory it does not support new versions of ABP as I was told. https://abp.io/docs/latest/cli/differences-between-old-and-new-cli#using-the-new-abp-cli
Volo.Abp.Cli is different from Volo.Abp.Studio.Cli and uses different templates as I had already reported https://github.com/abpframework/abp/issues/20388
In fact my question was whether Abp Studio and Abp Studio CLI share the same templates or use different templates as it happens with Legacy CLI.
-
0
In fact my question was whether Abp Studio and Abp Studio CLI share the same templates or use different templates as it happens with Legacy CLI.
ABP Studio and ABP Studio CLI(Volo.Abp.Studio.Cli) share the same templates but the legacy CLI (Volo.Abp.Cli) generates outdated templates.
-
0
In fact my question was whether Abp Studio and Abp Studio CLI share the same templates or use different templates as it happens with Legacy CLI.
ABP Studio and ABP Studio CLI(Volo.Abp.Studio.Cli) share the same templates but the legacy CLI (Volo.Abp.Cli) generates outdated templates.
Perfect, thanks!
