Hi all!
I want to know how you would structure your application if you want to create a new module.
I have a blank .Net Core 2.2 and Angular project. Front- and Backend are seperated.
I checked the modular todo app project (https://github.com/aspnetboilerplate/modular-todo-app) but it is 2 years old and I want to do some extra stuff.
Let’s say I want to have a master data module with the entities company and stores. I want to use the RAD tool and then "move" the created files to a seperate solution structure and pack it as a module. And after that I want to have another module called "Calculations" that depends on that module.
How would you structure your solution and what are the best practices to create a module?
Thanks in advance!
2 Answer(s)
-
0
Hi @christianw
Currently, we don't have a modular app example for ASP.NET Core & Angular version but you can use https://github.com/aspnetboilerplate/modular-todo-app for the server side modular arhcitecture. This is still a valid suggestion.
-
0
Hi @christianw, @ismcagdas
I would like to share my solution architecture structure with you and perhaps have some feedback. Let's take the example of an ERP system that has Sales and Purchase modules.
I would create two projects per module - one for the applications services and another one for data related logic (EF Core).
Any classes that need to be shared across Sales and Purchases will be created on the Common project.
I would make minimal changes and avoid adding new classes to the original AspNetZero Projects. This will allow me to easily upgrade to a newer version of AspNetZero.
Any feedback would be appreciated.
Thanks, Rui
