I've read many pages on Service vs Manager and checked the code but I'm not sure I get the difference between the Service and the Manage in ABP.
Here is my specific case: I have a "Function" object. A Function can have a list of Parameters.
When I insert a function in the database, I also insert its parameters at the same time.
How should that be handled? I already have a FunctionAppService that creates the function in the database. Now, how about the parameters. Should they be handled via their repository in the CreateOrEdit() method in the FunctionAppService ? Should I create a ParameterAppService even if entering only parameters doesn't make any sense because it is always linked to a function ?
Should the "Manager" play a role here ? I doubt it because the Manager cannot call the AppService because of the way the projects are linked (and we want to avoid circular reference).
I'm confused with the structure. I need some guidance!
Where is the right place to submit suggestions and corrections?
Here are suggestions:
Switch from jTable to DataTables.net. I know jTable is your product but it seems you have so much thing in your plate, jTable has ~1300 unsolved issues and, let's face it, it has many display issues.
On this forum, add a search box in the header. It is a pain to have to click on Search, then Advanced search, then wait to be able to write something in the box.
Here is a correction: On this page: <a class="postlink" href="https://aspnetzero.com/Documents/Developing-Step-By-Step-MPA#creating-person-application-service">https://aspnetzero.com/Documents/Develo ... on-service</a>
You are talking about ListOutputResult... but it does not exist. After some research, I think you renamed it ListResultDto. It looks like IInputDto was removed too (many months ago). I think this whole page and multiple projects (see your samples) need to be updated.
With all due respect, your product contains great code and nice way to do things and scale well. That said, the documentation and examples provided are not as clear as they should. In the end,a product like your is as good as its documentation. You may provided a great solution but if I can't figure out how to make it work without reverse-engineering your process, I don't have much gain.
I encourage you to update everything and I'm here to point what isn't working well if you need.
Thanks in advance.
