So this means once i added
Elsa.EntityFrameworkCore
Elsa.EntityFrameworkCore.SqlServer
to my host project when I run host project ELSA migration with be automatically applied?
I already downloaded demo app but demo app does not show how migration created and the way migration implemented to DB is different than abp approach
there is no such package Elsa.Persistence.EntityFramework.
packages names for elsa V 3 is
"Elsa.EntityFrameworkCore" Version="3.5.2" Elsa.EntityFrameworkCore.SqlServer" Version="3.5.2"
So how should related migration added to DB
Till now it’s not clear for me how Elsa Abp integration works?
If I added Elsa pro modules shall my host project will act as Elsa server?
Does this module production ready or still work in progress
I see this not practical solution to install pro modules to solution created by open-source version any how i migrated my code to new solution created by commercial version but i have issue installing ELSA workflow module when installing module empty DB migration created
Dear ABP Support Team,
I am requesting assistance regarding a consistent issue I am facing with module duplication when installing ABP modules into a solution that was originally generated using the ABP open-source version template.
When adding commercial/pro modules such as the Account Admin, Account Public, and other Account-related modules, the framework reports duplicate registrations and conflicts across the DomainShared, Domain, ApplicationContracts, and Application layers. These duplications occur even when following the documented dependency structure and recommended layering.
The main symptoms include:
Duplicate localization resource registrations
Duplicate module dependencies being detected
Errors such as: “Resource already added,” “Module already registered,” or similar conflicts
Module layering inconsistencies caused by mixing open-source and commercial package sets
At this point, I am unable to cleanly integrate the required modules into the open-source solution without manually restructuring dependencies or removing modules that should normally coexist.
I would appreciate your guidance on:
Whether additional steps are required when integrating commercial modules into a project created from the open-source startup template.
Whether there are known compatibility gaps or required configuration changes between OS and commercial module sets.
A recommended or officially supported module dependency structure that prevents cross-layer duplication.
Any patches or upcoming updates that will address these module registration conflicts.
Please advise on the best path forward so I can proceed with a stable and maintainable module configuration.
