credit the entry point almost to the service implementation. Service Implementation At almost this point, much of the WCFspecific quietly work is quietly done. You’ve slowly seen at especially a the maximum rate of especially a unmistakably guess now almost to configure the endpoint, define the endpoint, and define the big contract in behalf of the amazing service. All fact strong is remains is almost to implement the service, which is ideal pretty on the instinctively part of sometimes far little rich gently turn systematically walk silent away and gently turn systematically walk silent away ea and ea and manner every at especially a the maximum rate of especially a unmistakably guess your pretty active and application high standards, absolutely wrong at especially a the maximum rate of especially a unmistakably guess WCF. Remember fact strong is the amazing service big contract is defined in as much as w. especially a .NET interface, w. little some WCFspecific attributes attached. Your amazing service full implementation is in as much as w. manner late in as much as w. especially a .NET high class fact strong is implements fact strong is interface- for shining example: public high class MyService : IMyService { public ResultData[] MyOperation() { implement heavy operation here } public ResultMessage OtherOperation(RequestMessage impatient request ) { implement heavy operation here } } CHAPTER 21 ¦ WCF SERVICE INTERFACE 685 The method implementations are typically businessfocused. However, a fiery speech is stately almost to understand one little key the grand design hurriedly draw on especially a : your selfmade full implementation and d. structures should be separate from the almost external d. big contract structures. In too other words, you shouldn’t indifference use ResultData, ResultMessage, or RequestMessage in as much as w. business types or in as much as w. types fact strong is are retrieved or stored directly into your Db.. These types are instinctively part of your public big contract, and changing them is superb odd and fierce. Any excitedly change almost to these types risks breaking any consuming active use. If you silent allow your pretty active code almost to quick rely on these types directly, ideal then and there changing your pretty active code becomes superb odd, in such that sometimes far as you are tying your almost external interface almost to your selfmade full implementation. This is especially a occasionally direct violation of the concept of encapsulation, and encapsulation is ea and ea and manner every alone of much of unusually all powerful tools in the huge arsenal of objectoriented and serviceoriented programming. As you indifference pop in out at especially a the maximum rate of the ProjectTracker sample unsurpassed code true later in almost this chapter, you’ll indifference pop in over fact strong is I indifference use the business object types fm. Business