Hi, Suppose we have person entity that use in different solution. How can I create a Module that contain person entity definition (Entity, AppService, Views and ...) to include in all solution?
6 Answer(s)
-
0
There is a sample for that. Did you checked it: <a class="postlink" href="https://github.com/aspnetboilerplate/sample-blog-module">https://github.com/aspnetboilerplate/sample-blog-module</a>
-
0
Thank you man. I will check it. Your framework is awesome.
-
0
In order to learn the framework, I'm implementing a sample project I did some time ago. It would be have some core functionality, available to all tenants, with three modules (with associated features) of optional/premium functionality. Based on the documentation, it looks like the suggested structure is to develop the optional modules in separate assemblies from the core. Is this correct? Assuming so, do you happen to have an example of this (modules in separate assemblies)? In the Blog sample, the module is in core assembly.
-
0
Hi,
Blog module is a seperated module from the main application. Blog module is also layered. Abp.Samples.Blog.Core is the Domain layer of Blog module. Also, there is a sample application which uses blog module. It's domain module definition is here: <a class="postlink" href="https://github.com/aspnetboilerplate/sample-blog-module/blob/master/app/MyAbpZeroProject.Core/MyAbpZeroProjectCoreModule.cs#L10">https://github.com/aspnetboilerplate/sa ... ule.cs#L10</a>
-
0
Ah, now I get it. The blog sample isn't just a different project, it's a whole different solution. Now I understand. This is the recommended approach, yes?
-
0
Depends on your case. If you prevent layering for also your modules, yes this is the right approach.
