Yeah the only options you have as far as I can see are what Lightning suggested or the obvious... combine them both in the same service I guess it depends how much separation you need between the two things that the services deal with (in this case: Customers and Employees) - I wouldn't personally go just creating a separate service for every single category of item in your program (unless you have an awful lot of methods in each one) for this precise reason... but then I have only created small programs using WCF so far, so I guess im not the best person to offer advice on the design.
I don't see how that's a problem. I think you might have misunderstood the concept of services here... when you create two services, you create them separately because they serve different purposes. They are therefore two different services, they just happen to sit in the same 'project' or virtual directory in IIS. You'll need both references in place. If you want one reference, you need one service. It's sort of like saying "Well, I have a User class and an Orders class... why can't I just use one class for both?" (Because it doesn't make sense)
Alternatively, you could always move the interface classes out into another class library and references those and then call the services via an IClientChannel but that sort of defeats the purpose of WCF IMEO.
Reply With Quote
I guess it depends how much separation you need between the two things that the services deal with (in this case: Customers and Employees) - I wouldn't personally go just creating a separate service for every single category of item in your program (unless you have an awful lot of methods in each one) for this precise reason... but then I have only created small programs using WCF so far, so I guess im not the best person to offer advice on the design.
