Hello, first of all, I am very sorry for such a late reply, this was somehow overlooked. If your problem still persists I can make some suggestions?
Hello, first of all, we apologize for the late response. We normally respond much sooner, usually within the same day (unless it's a weekend), but in rare cases it can be overlooked and I apologize for that.
The relevant mate will reply as soon as possible. Thank you for your patience 🙏
It worked but When I try to create a project I get the following error. How can i see logs ?
You can find the log file in .abp/studio/ui/logs/abp-studio-ui-logs.txt.
The new version is released, you can try to verify if the problem occurs again.
The problem will be fixed in the next version 🥳 I will let you know here after the release.
Unfortunately, I haven't solved the problem completely, but I'm experimenting. Even if it is not definite, we can release a version today. If the problem is successfully solved in the tests I do before this release, it will be included in the release, if not, unfortunately it may be waiting for next week.
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.
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
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.
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 8 only 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.