Could you tell me the advantages / disadvantages of these two implementations?
My context: we have a large project that includes many different domains. Each domain will naturally be a domain. But many teams of different teams will work on each, and we want to separate business rules. What is the best way to manage these ares in a solution?
I have seen many examples of areas in a separate project or with portable areas. But I can’t make a decision.
From my point of view:
Separate project
- Plain
- Difficult to manage content (JS, CSS, ...). Should it be on the main site?
- Best performances
Portable areas
- All content, views should be in one project
- Possible duplicate code between areas
- Disadvantages: name, embedded resources, ...
- MVC Contrib: ?
- :
,