If I create a domain service, do I put that class in the Application project? If not, where? Core, Core.Shared? Application.Shared?
If I need this domain service to be usable by the Public website (for getting and updating entities), is that still the correct location? If not, where? Web.Core?
If the public website needs to update an entity based on input from a browing user that is NOT logged in, will a simple unit of work allow that to happen?
Does this unit of work need to exist in the Public controller or in the domain service?
Thanks!
2 Answer(s)
-
0
hi Please refer to the domain service documentation first. : ) https://aspnetboilerplate.com/Pages/Documents/Domain-Services
-
0
I have successfully accomplished this.
For anyone looking on how:
In Core project, next to your entity, you can create a domain service there, inheriting from workDomainServiceBase
Then, bring that into your appservice (in Applications).
Then, move methods required for your domain service from Applications, and have those methods call the function in the Domain service.
This will let you put certain methods "on an island" as needed.
