I have been working with WCF services over the last year, moving our system over to a WCF service implementation. However, with the scope of the project, in maintaining OO principles, we have erected many endpoints and interfaces; leaving many service client declarations, and many many configuration woes that can appear with having numerous enpoint configurations and representations.
I have been looking for an example of creating a single endpoint configuration which will encapsulate sections of WCF, however I have not been able to find something that fits what I have been invisioning.
I was wondering if anyone has successfully represented a service system in this way.
Where Service contains OO based interface definitions and partial(or full) classes that expose the action of the interfaces.
I have a sneeking suspission that I may need to create a client application and provide the interface representations at a more base level, however I want to avoid creating a in shop client, as apposed to something the language itself could provide.
View Complete Post