there isn't much boilerplate code given each object has a specific context.
I haven't worked with S#arpArchitecture. My only caution is not to use it unless you understand why it works the way it does. If you understand the why you can then make a well informed decision about if you should use it. and as Gunnar stated: contextually specific DTO's are a huge advantage. yes, you end up with dozens of little POCOs but they are much easier to maintain. Changing a single domain object that affects multiple end points is much more complex than changing a single DTO that affects a single end point. You can also begin to introduce conventions into your application because each DTO is highly specific (ideally each DTO has exactly one purpose). automapper also goes a long way of reducing the repetition of mapping domain entities to DTOs. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/JqUe_7xu9WYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
