Last post Aug 11, 2013 09:57 AM by Rion Williams
Aug 11, 2013 06:32 AM|developer250|LINK
Aug 11, 2013 06:46 AM|MetalAsp.Net|LINK
I don't know about ALWAYS but I do think it's the right thing to do. I like to have entities/objects to work with. Some times you might even use different types of objects. You might have the database entity/object and you might have a display object, or
Aug 11, 2013 09:57 AM|Rion Williams|LINK
As MetalAsp.Net mentioned, always is a very strong word.
I believe that the more that you break your project down and seperate your entities into distinct areas, it can help make your code not only easier to read (to understand what is going on) but easier to write as well. It ultimately will depend on
your usage and perferences.
It's completely safe to have all of your entities defined in a single area and pass them around so that your entire application refers to a specific entity by a certain class, but if you want to seperate them into different objects for specific areas that
is acceptable as well (this will allow you greater control by only pulling the data that you need for the specific area you are targeting).
More specific DTOs is likely the route I would recommend, but as I have said previously, it's up to your personal perference.
You may want to take a look at the following resources on the topic as well :