I'm exploring WCF, trying to find my feet and decide if it's the right architecture for our project. We are looking at having a WCF service that provides a central point of access for various clients, including WinForms, ASP.NET and Silverlight 4. We are
using self-tracking entities (STEs).
I have tested out a solution in which I can have a WCF service and use it from WinForms and ASP.NET without any problems. I used the STE T4 template, and put the STEs in their own class library, which I referenced from the client project. This all worked
I ran into trouble trying to build a Silverlight 4 client to access the same WCF service. It seems that SL can't reference a non-SL project, so I can't use the same STE project as I used in the other client. I added a SL class library, hoping I could use
that in the non-SL clients, but this didn't work.
So, it looks like I am going to have to have two separate WCF services, one that sends out plain old STEs, and one that uses a SL version if I want to get this to work. Frankly this is unacceptable, and one of the main points of having a single point of
access was consistency. If we have to maintain two separate services, we lose a lot of that.
I have searched in vain for an answer to this, which surprises me as I would have expected many people to want to do such a thing.
View Complete Post