There is a recommendation that transfer objects should not contain object references to other transfer objects. Instead, they should use the primary keys of the other transfer objects as foreign key f
I have a repository layer that i开发者_JAVA技巧s responsible for my data-access, which is called by a service layer. The service layer returns DTOs which are serialized and sent over the wire. More of
I have the following code to query an EntityContext (through a repository) and map it unto a DTO: public class QueryQuestionsConsumer : IConsumerOf<QueryQuestionsRequest>
Closed. This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing
First of all sorry my bad English! I see in many Silverlight tutorials the following: We have models on the server side for example Product. The webservice has a method for example Ilist GetProducts(
I have a RESTful web service that responds to /user/{userId} with a marshalled XML representation of a User domain object (using JAXB). What\'s an appropriate way of communicating back to the client a
I\'m wanting to开发者_Go百科 know if it\'s a bad design to use repositories when converting DTOs to their domain object counterpart.
I have 1 dto, statEMailDTO, which has a field that holds the Field Names of what I\'m looking for (they are comma delimited.
I\'ve been looking at a lot of WCF examples using EntityFramework and most of them seem to return some kind of POCO or DTO class to the cl开发者_开发知识库ient.
I\'m trying to figure out the best approach to architecting this project. Basically, it\'s a \"band\" profile site. I\'m using ASP.NET 4, EF, and Automapper (structuremap too, but that\'s not importan
加载中,请稍侯......