I am just getting started with Prism, after building traditional apps structured around domain-driven design. I have typically put my domain model and data-access layer in separate projects. The Prism documentation suggests that I should partition my
model and data-access, and then incorporate the relevant portions into each module.
What is considered best practice?
-- Treat a domain model and data-access as cross-cutting concerns, and keep them in their own loosely-coupled projects?
-- Partition them and incorporate them into the app's modules?
If there is no clear best practice, what would you see as the pros and cons of each approach? Or, if the answer is "It depends", on what sorts of things would it depend? Thanks for your help.