Hi, is there a good sample to start from that shows a separate module project? I would like to add my own Partner and Vendor module project and I feel like I should be able to define all of my new entities and UI there. I would like to enable the UI with a user permission.
I have found this doc on module definitions … https://aspnetboilerplate.com/Pages/Documents/Module-System
I have found this sample that comes very close to what I want … https://github.com/aspnetboilerplate/sample-blog-module Is this the preferred way of doing this?
Am I over-thinking this? Or would I be better off just adding all of my new entities into my exisiting *.Core project in a new Partner folder? I am not sure how big this application will get down the road and I feel like I want to keep all of my new stuff separate. Thanks --Andy
2 Answer(s)
-
0
Hi, it depends on how you want to design your module.
- should it be agnostics of how your aspnetzero project works? if yes, see https://aspnetboilerplate.com/Pages/Documents/Plugin
- should it be replacing/enhancing the existing implementation? if yes, see https://github.com/aspnetboilerplate/aspnetboilerplate/tree/dev/src/Abp.AspNetCore.SignalR/AspNetCore/SignalR
-
0
Thanks, those links help. The blog sample project comes close to what I was thinking ... I'm just deciding if the effort to keep it separate like that is worth it my case.
