Activities of "EngincanV"

Hi @sekmenhuseyin, thank you for the detailed error explanation and your feedback. We are doing our best to test and release a stable product. However, due to various configurations, different UI types, solution templates, manual configurations, old Suite configs, etc., it is difficult to address all issues during the testing process.

I will create a new issue to fully test ABP Suite in various project configurations, UIs, and related scenarios, and we will work on resolving the existing problems.

Regarding the issue you reported: I created the same solution named Sekmen.Goo with identical configurations and could not reproduce the problem:

It occurred to me that the issue might have arisen because you previously created a solution named Sekmen.Goo with different configurations in the same root directory. As a result, ABP Suite may have mismatched your current solution with the earlier one. For instance, if you had previously created an Angular solution with the same name, ABP Suite might expect the HttpApi.Host project in the solution for code generation.

To resolve this, please return to the homepage of ABP Suite (click on the logo), remove the current Sekmen.Goo solution, and add it again (you can also close and reopen the tab if using ABP Studio).

After regenerating the pages, everything should work as expected. Please let me know the final result.

Best regards.

[igomez] said: Hi Engincan,

It's not a problem to solve the extended code broken.

However what we need to understand, and make it work is the ABP Suite.
Why does it fails continuously the "Save and generate" process?

We have repeated the process of deleting the solution, cloning it again, even starting with a blank DB, however does not matter the change we make in the entities, it fails to complete the process.

What do we need to do to have ABP Suite working with no errors?

Thanks

Hi, if you select the custom code support option, ABP Suite regenerates only the files that do not end with the *.Extended.cs extension, and it regenerates only the constructors in the extended files when required. Any other changes to these files are your responsibility.

Does the issue occur in the extended files, or in other files that ABP Suite should normally regenerate but does not? Could you clarify? From what I understand and from what I’ve tried, it seems that the extended files were updated manually, rather than ABP Suite being unable to generate changes elsewhere.

Regards.

[igomez] said: Hi,

As informative: my dotnet-ef version is 9.0.1

Also in EntityFrameworkCore.csproj we have this versions:

I've done the following:

1. From Terminal in my EntityFrameworkCore project, run the dotnet ef migrations add New_Migration and it completed successfully
2. After that, I opened ABP Suite, added a new navigation and when clicking on "Save and generate" it failed again
3. Tried from Terminal in EntityFrameworkCore project to clean, restore and build, and got a build error

I'm not sure how to move forward on this.

When you add a new property, you should update your DocumentManager.Extended.cs file manually. Because, it's a custom code class and ABP Suite does not make any changes on *.Extended.cs classes. (https://abp.io/docs/latest/suite/customizing-the-generated-code)

[igomez] said:

[EngincanV] said: support@abp.io

Hi. Done, solution shared by email

Hi, thank you. I got your email and downloaded the solution yesterday. After I got your solution, today, I've tried to generate new CRUD pages just now, and it successfully generated the required code and migrated to the database (added two new properties, like in the figure below):

Your database problem might be related to a temporary connection issue. Or if you have updated the dotnet-ef tool recently, it might be related to that. Can you please check these?

dotnet-ef --version

dotnet-ef version is 9.0.11 in my machine. It should be 9.0.* to successfully create migrations for v9.x.x. If it's in the correct version, please navigate to your ef core directory and try to create a new migration (via command: dotnet ef migrations add New_Migration) and then run the dbmigrator project to update your database.

Regards.

Hi again @igomez, I have tried with a tiered solution but could not reproduce the same problem that you faced with. By any chance, can you share your solution via email to support@abp.io website with the ticker number? So, I can check it from your solution. Waiting for your reply.

Regards.

[igomez] said: not sure why this is closed, reopening...

Hi, sorry for the inconvenience. Our support bot automatically closes questions due to inactivity. I'll try to reproduce your problem and write back to you asap.

Regards.

Hello again, I got a quick update: We released v10.0.1 yesterday, so you can update your ABP Suite version and generate CRUD pages as before.

Regards.

[merdan] said: Manually downloading Microsoft.ClearScript.V8.Native.win-arm64 nuget package and extracting ClearScriptV8.win-arm64.dll to the ..\volo.abp.suite\10.0.0\tools\net10.0\any\runtimes\win-arm64\native folder fixed the issue.

While this workaround works, still keeping this issue open so that an ABP developer can fix this in future releases.

Hi @merdan, thanks for the quick reply. We will fix this asap, thanks for reporting. (refunded your ticket)

Does ABP Suite support generating a full 3-level child hierarchy (With Master-Child) (e.g., Lesson → Tests → Questions) with the Angular as frontend ?

Hi, currently ABP Suite does not support 3+ level master-child relationship. A master can have multiple child entities associated with it but unfortunately, in the current design, you can't make a child entity as a master entity of an another entity.

Regards.

Hi, apologies that the thread was closed earlier (our bot automatically closed the thread because after the latest AI bot response, there was no activity in the question).

From a best practices standpoint, you are correct that the constructors of entities should be marked as internal rather than public, given that we also create domain services and the core logic resides there, so no need to make them public. I will create an issue to address this.

Regards.