This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

Note

It is also possible to host a WCF service using the Vista-specific Windows Activation Service (WAS).

Consult the .NET Framework 3.5 SDK documentation for details.

The final assembly represents the client that is making calls into the WCF service. As you might

expect, this client could be any type of .NET application. Similar to the host, client applications also

typically make use of a client-side *.config file that defines the client-side plumbing. 

Figure 25-4 illustrates (from a very high level) the relationship between these three interrelated

WCF assemblies. As you would assume, behind the scenes are several lower-level details used to

represent the required plumbing (factories, channels, listeners, etc.). These low-level details are

most often hidden from view; however, they can be extended or customized if required. Thankfully,

in most cases, the default plumbing will fit the bill.

Figure 25-4.

A high-level look at a typical WCF application 

It is also worth pointing out that the use of a server-side or client-side *.config file is techni-

cally optional. If you wish, you can hard-code the host (as well as the client) to specify the necessary

C H A P T E R   2 5