أنشطة "vincent.goh"
There's a bug in ABP Suite 4.4.3 where the entity creation feature results in a wrong namespace in the *.Blazor/Pages/[microservice_name]/[entity_name].razor.cs file.
The correct namespace generated should be *.[microservice_name].Blazor.Pages.[microservice_name] instead of *.[microservice_name].Blazor.Pages
By the way, I just realized that EF Core 5 removes the need to code associative entities for many-to-many relationships between Entities. This helps to separate the domain model from the data model.
https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-5.0/whatsnew
Thanks Halil for your clarifications! It's most helpful.
One feature I would like to request in the ABP Suite is to allow the creation of an Entity with composite keys rather than a primary key, as shown in the screenshot below.
This will greatly assist in creating associative entities that use a composite key, like in the case of AbpUserRole where UserId and RoleId are used for its composite key.
Thanks for your explanation on the use of Value Objects in DDD. These are useful information.
My question is more about whether Value Objects should be used for associative entities in a SQL database. On page 28 of Halil's ebook, he used Value Object for an associate entity called "IssueLabel". See diagram below.
However, when I looked at ABP framework's own implementation of such associative entities like AbpUserRole or AbpUserOrganizationUnits, Entities are used instead of Value Objects.
Just wanted to know if associative entities/tables that map relationships between entities should be using Entities or Value Objects in ABP framework as Halil seems to be suggesting something different from the actual implementation in his ebook.
Thanks.
Best regards, Vincent
I have read the "Implementing Domain Driven Design" ebook and have some questions on how to use and implement Value Objects in ABP according to DDD, particularly in persisting Value Objects in database.
On page 28 of the ebook where there's an example of IssueLabel as a Value Object, it seems to suggest that Value Objects should be used to implement associative entities / bridging tables to establish one-to-many or many-to-many relationships between entities.
However, I don't see the option of creating a Value Object using the CRUD Page Generator in ABP Suite and I don't see any examples or documentation of how Value Objects should be coded in ABP for persistence in a DBMS like SQL Server. As a result, I have been creating Entities for associative entities / bridging tables for my current ABP solutions.
Any advice on implementing Value Objects in ABP and storing it Value Objects in SQL databases will be helpful. Thanks.
Is there an easy way to create a new microservice using the ABP Suite?
Instead of the standard "product" service created as part of the microservices solution template, I would like to create a microservice named something else.
- ABP Framework version: v4.4.0
- DB provider: EF Core
- Exception message and stack trace:
- Cannot read the template Volo.Abp.Commercial.SuiteTemplates.Templates.Frontend.Mvc.Menu.MenuContributor_ModuleAddMenuItem_Method_Microservice.txt
- Steps to reproduce the issue:"
- Launched ABP Suite v4.4.0
- Added /services/product (an individual service of a microservice solution) as an existing solution in ABP Suite
- Tried adding a new entity in the CRUD Page Generator
- The "Save and generate" button gave the above error
I've created a microservices project via ABP Suite v4.3 using Blazor WebAssembly for the UI.
I don't want to use the Lepton theme that comes with it and I want to implement my own theme instead. However, I am having difficulty finding documentation for how to implement my own theme in the created solution.
The only relevant one I can find is https://docs.abp.io/en/abp/latest/UI/Blazor/Theming#implementing-a-theme but this only talks about replacing the basic theme from ABP Framework, and not the Lepton theme from ABP Commercial in a microservices solution.
Could you point me to resources that can help me with this? Thanks.