Factories, or Dependency Injection for object instantiation in WCF, when coding against an interface?

We've discussed doing this internally for enterprise apps where we control both sides of application, as a productivity gain, for . NET clients. Jury is still out on this one.

I've come across the same question in my WCF development. The fact is there must be a concrete implementation of your data contracts on both sides of the communication. So where do those implementations come from?

On the server side, the implementations are typically your business objects, with all of their business logic and so on. And you don't want to use those implementations on the client--that would mean putting them in the shared assembly, and you don't want that for several reasons. So the client needs its own, separate set of concrete classes.

Either you're going to write them yourself, or you're going to have them generated automatically.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.