ABP Framework version: v9.0.3
- UI Type: ABlazor WASM
- Database System: EF Core (PostgreSQL, etc..)
- Tiered (for MVC) or Auth Server Separated (for Angular): yes
In your documentation you state that any implementation of the FeatureDefinitionProvider is "Generally created in the Application.Contracts project of your solution", but if I look at ABP's source code (we have purchased a commercial licence and all the source), I see that more times than not you folks have the implementation of this class in the Domian.Shared project of your solutions. Why is that? What's the advantage of it being in one project or another?
https://abp.io/docs/latest/framework/infrastructure/features?_redirected=B8ABF606AA1BDF5C629883DF1061649A
1 Answer(s)
-
0
Hi,
Usually created in
Application.Contractsproject.If you need to check the features at the
Domainproject, put it inDomain.sharedproject.Like the definition of permissions, it is usually placed in shared projects. Whether it is
Application.ContractsorDomain.shared, they are shared projects
