I got the same problem. I use Castle. Windsor IOC container + "PerWebRequest" lifestyle, and it works in a similar way as your factory under the hood I'm still trying to find the perfect solution for my needs, but I have an intermediate solution that can help you : making your WCF service run with a HttpContext : 1) In your WCF project, ask for ASP.Net compatibility system.
ServiceModel> Required) public class MyService : IMyContract { ... } Source : Code rant.
I got the same problem. I use Castle. Windsor IOC container + "PerWebRequest" lifestyle, and it works in a similar way as your factory under the hood.
I'm still trying to find the perfect solution for my needs, but I have an intermediate solution that can help you : making your WCF service run with a HttpContext : 1) In your WCF project, ask for ASP. Net compatibility 2) Add an attribute to your service to manage this compatibility AspNetCompatibilityRequirements( RequirementsMode = AspNetCompatibilityRequirementsMode. Required) public class MyService : IMyContract { ... } Source : Code rant.
I'm writing a simple movie database which has a three tier stack of service layer, data access layer and SQL DB. I'm using LINQ to SQL to access the DB and return a Film from the Film table in the DB. This will then be returned as a Film object from the DataContracts in the service layer.
I thought this would work ok, but its resulted in some awkward code which doesn't look right. Can someone sanity check this please? Is it best practice to map every LINQ result to it's DataContract?
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.