Running the Windows Communication Foundation Samples
The Windows Communication Foundation (WCF) samples can be run in a single-machine or cross-machine configuration. As supplied, the samples are ready for running on a single machine. In a cross-machine configuration, it is necessary to modify a sample's configuration file settings. The following procedures explain how to run a sample in same-machine and cross-machine configurations. Note that there are variations in the steps for services hosted in Internet Information Services (IIS) and the self-hosted samples. Most samples are hosted in IIS; see the sample readme information to determine how it is hosted.
On Windows Vista, samples that are not hosted in IIS require elevated privileges to register a listener with Http.sys. Use Httpcfg.exe to register the service's listening addresses with the account the service is running under, or launch the service from a command prompt running with administrator privileges.
Before building or running any of the WCF samples, be sure you have performed the One-Time Setup Procedure for the Windows Communication Foundation Samples.
To run the sample on the same machine
If the service is hosted by IIS, ensure that you can access the service using a browser by entering the following address:
http://localhost/servicemodelsamples/service.svc. A confirmation page should be displayed in response. If the confirmation page is not displayed, see Troubleshooting Tips for WCF Samples.
If the service is self-hosted, run Service.exe from \service\bin, from under the language-specific folder. Service activity is displayed on the service console window.
Run Client.exe from \client\bin\, from under the language-specific folder. Client activity is displayed on the client console window.
If the client and service are not able to communicate, see Troubleshooting Tips for WCF Samples.
To run the sample across machines
If the service is hosted in IIS:
On the service machine, create a virtual directory named ServiceModelSamples. The batch file Setupvroot.bat included with One-Time Setup Procedure for the Windows Communication Foundation Samples can be used to create the disk directory and virtual directory.
Copy the service program files from %SystemDrive%\Inetpub\wwwroot\servicemodelsamples to the ServiceModelSamples virtual directory on the service machine. Ensure that you include the files in the \bin directory.
Test that you can access the service from the client machine using a browser.
If the service is self-hosted:
On the service machine, create a directory to hold the service files.
Copy the service program files from the \service\bin\ folder, under the language-specific folder, to the service machine.
In the service configuration file, change the address value of the endpoint definition to match the new address of your service. Replace any references to "localhost" with a fully-qualified domain name in the address.
Launch Service.exe from a command prompt.
Copy the client program files from the \client\bin\ folder, under the language-specific folder, to the client machine.
Set the endpoint address.
If the service is not running under a domain account, open the client configuration file and change the address value of the endpoint definition to match the new address of your service. Replace any references to "localhost" with a fully-qualified domain name in the address.
If the service is running under a domain account, regenerate the client configuration by running Svcutil.exe against the service. For more information about running Svcutil.exe, see Building the Windows Communication Foundation Samples. Use the generated file instead of the configuration file in the sample. The generated configuration file has additional identity information, and contains all settings necessary to connect to the service endpoint even though they are the default settings. For more information about identity information, see Service Identity and Authentication, and <identity>.
On the client machine, launch Client.exe from a command prompt.
To debug a service
Build the solution (both client and service) using the Build menu or CTRL+SHIFT+B.
If the service is hosted in IIS:
Activate the service using a browser by entering the address
In the solution, choose the Debug menu and the Attach to Process menu item.
Select the Show processes from all users check box.
Select the host worker process W3wp.exe to debug (select ASPNet_wp.exe on Windows XP).
You can now set breakpoints in the service code and enable breakpoints on exceptions.
Right-click the client project item and choose Debug, Start new instance.
To clean up after the sample
- If the service is hosted in IIS for security purposes, remove the virtual directory definition and permissions granted in the setup steps when you are finished with the samples.