Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
i am about to develop a small application that should consist of a server and a rich client. so far i will follow the following design guidelines:
Our users need to be able to export data in CSV format, edit some of the records, and upload the data again. The data does not map to entities, you could say that the object graph is flattened to fit
6 months ago , i was asked to make a database access for our project that has around 30 tables ,( using the Data transfer objectpattern ) . we were using Microsoft\'s sql server back then. so i had to
I would like to flatten a collection of DTO\'s into a single DO using LINQ, but my LINQ-fu is weak. My DTO looks like this:
I have an MVC2 n-tier application (DAL, Domain, Service, MVC web) using a DDD approach (Domain Driven Design),having a Domain Model with repositories. My service layer uses a Request/Response pattern,
I\'m designing a C# application Presentation ( web site + flex apps ) Business Logical Layer (might be WCF to enable multi client platforms)
I have some persistence capable Java objects with all the @annotations in my web application. All these objects reside in a data layer. Is it a best practice to use these persistence objects as data t
I have a collection of WCF web services that share a common DTO model. The problem is that when I add service references in Visual Studio 2010, the proxy generated for each of the web services has i
I\'m using DTOs between my business and presentation layers and have some mapping code in the service that converts DTO <-> domain object. I\'m currently allowing the PL to partially populate a DTO
加载中,请稍侯......