You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mr @hikalkan
Hi,
Why we need two type of same module? In your design, modules are just library references and they need an extra application for running? Isn't possible to implement Host services in their own module?
How we can access to our module's api end-point by pushing F5 without having demo app in our module's solution?
The text was updated successfully, but these errors were encountered:
Modules are libreries as you said. They are not runnable applications. A module does not assume how it will be run, the final application decides it. You can run a module as a self deployed service or as a part of a monolithic application. See https://abp.io/documents/abp/latest/Best-Practices/Module-Architecture#layers-packages for possible usages of a module.
In addition, the application will make configurations, prepare the asp.net core pipeline and many other tasks those should not be assumed by a module. Demo applications in the modules are sample minimalist example applications use the module.
Also, most of the times, modules needs each other. For instance, blog module needs to a user & permission management system. Identity module is an implementation of the user management module. But we don't want blog module directly depends on the identity module. So, the application brings modules together and prepares a fully running application.
Mr @hikalkan
Hi,
Why we need two type of same module? In your design, modules are just library references and they need an extra application for running? Isn't possible to implement Host services in their own module?
How we can access to our module's api end-point by pushing F5 without having demo app in our module's solution?
The text was updated successfully, but these errors were encountered: