CODEWITHSUNDEEP
c#.netasp.net-mvcwcfdto
user3711357
user3711357

Reputation: 1625

What should keep into this design approach

My Project solution is as below:

  1. MVC Project (Containing reference of both projects listed below)
  2. WCF Service containing business methods (Containg reference of below listed project)
  3. Common Project for DTO or BusinessOBject

IN MVC - Calling the WCF service method is as follow - IList<Employee> RetriveData() it is called from MVC - ServiceClient.RetrieveData() , now problem is return object Employee point to ServiceHost.Employee object instead of - Common.DTO.Employee object (Library project) so, it gives type casting error.

Can any one suggest me what is the solution over here or i should remove "Common.DTO" project refernece from MVC and only use Servicehost.Employee object.

Please guide me on this design, what should use.

NOTE: all objects are DATACONTRACT (serilizable). In MVC applicaiton, after retrieing DTO object, i do convert them into Viewmodel (It also internally refer any collection object like IList<ServiceHost.LookupItem> . Does it ok to use all generated serilized object directly OR , do i have to convert/cast each return object into common.DTO. object and then convert into ViewModel ?

Thank You

Upvotes: 0

Views: 85

Answers (2)

user585968
user585968

Reputation:

Don't use Visual Studio's Add Service Reference. Doing so will result in multiple types being defined in the solution and client-proxies that over time will become out of sync.

It is much better to define a common contracts assembly that your whole solution uses.

Please see WCF the Manual Way…the Right Way specifically page 3

You should try to follow patterns such as canonical data model whenever possible. This means the same type for POCO ORM; WCF; and as aggregates in your view model. Data conversion is expensive; leads to increased maintenance and possible fidelity loss. http://www.soapatterns.org/ http://www.eaipatterns.com/

Upvotes: 1

James
James

Reputation: 82136

This really depends on what level of abstraction you want.

If ServiceHost.Employee is your domain model and MVC is your presentation layer then it would make sense to use a DTO to bridge the gap here. Given that's the approach you seem to want to use then the solution would be to have ServiceClient.RetrieveData return IList<Common.DTO.Employee> instead of IList<ServiceHost.Employee>.

Upvotes: 0

Related Questions