Activities of "EngincanV"

Hi, I've reproduced the problem just before and will create an issue to fix it. It will be probably included in the patch release and I've refunded your question credit. In the meantime, you can manually fix the problem. Sorry for the problem and we will fix it asap.

Best regards.

[hassan.abuhelweh] said: Hello Any update on this ticket. Please help

Hi, we have fixed the problem and it will be included with the patch release. So, we should wait for the patch release.

Regards.

Hi again, I have tried it and it did not work as you said. I've created an issue for that and we will fix this problem asap. (I refunded your ticket)

Regards.

[hassan.abuhelweh] said:

Hello @EngincanV

Please advice, we are stuck for the last 4 days

I'll test it today and let you know.

[hassan.abuhelweh] said: I found the file but and I added the .dll but still not working
{ "Modules": [ { "DomainProjectDllFileName": "Persona.MasterData.Domain.dll" } ] }

Please advise quickly because we are stuck and time wasted

Hi, can you explain the problem? Does it not list the entities from the domain project or does it list it but when you try to establish 1 to n, then it creates build problems etc... ?

[hassan.abuhelweh] said: I found the file but and I added the .dll but still not working
{ "Modules": [ { "DomainProjectDllFileName": "Persona.MasterData.Domain.dll" } ] }

Please advise quickly because we are stuck and time wasted

Does the Persona.Enrollment project have dependency to the relevant domain package? Probably not and it seems this is the reason. You should ensure that and try again, it should work but if you get problem, let me know.

Regards.

Hi, in your root folder's suite directory, there should be a module-entity-extension.json file with an example configuration for you. You can pass the related domain dll (MySampleModule.MyProject.Domain.dll) with the module name and let ABP Suite to scan for the domain dll and list the related module entities for you.

Then, the related entities should be listed there, this is the way to extend the system's module entity listing functionality. (I noticed that it's not documented yet, and I'll document it asap, if you need help please let me know)

Regards.

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)