Goals:

• Demonstrate a solution using WCF services.
• Present available hosting models: WAS, IIS, Windows service, and managed application.
• Demonstrate some of available bindings: netNamedPipeBinding, netTcpBinding, basicHttpBinding, and wsHttpBinding.
• Demonstrate tracing and message logging.

Steps:

1. Create a new WCF Service Library, named ThirdService:
   
   • Add to the solution a new Class Library project, named ThirdCommon.
     • Add to the project a reference to the System.ServiceModel and the System.Runtime.Serialization assemblies.
     • Rename the Class1 to ThirdType. Define it as follows:
       [DataContract]
       public class ThirdType
       {
           [DataMember]
           public string StringValue { get; set; }
       
           [DataMember]
           public DateTime DateTimeValue { get; set; }
       
           [DataMember]
           public int IntValue { get; set; }
       }
     • Add the IThirdService interface to the ThirdCommon project:
       [ServiceContract]
       public interface IThirdService
       {
           [OperationContract]
           DateTime GetDateTime();
       
           [OperationContract]
           ThirdType GetThirdType(string s);
       }
   • Modify the ThirdService project:
     
     • Remove the IService1.cs and Service1.cs files.
     • Add to the project a reference to the ThirdCommon project.
     • Add to the project a new class named ThirdService, implementing the IThirdService interface:
       class ThirdService : IThirdService
       {
           DateTime IThirdService.GetDateTime()
           {
               return DateTime.Now;
           }
       
           ThirdType IThirdService.GetThirdType(string s)
           {
               ThirdType third = new ThirdType();
               third.DateTimeValue = DateTime.Now;
               third.IntValue = s.Length;
               third.StringValue = s + "_modified";
               return third;
           }
       }
     • Modify the App.config file. Its content was automatically generated with information about the IService1 interface. Find and replace all occurrences of 'Service1' to 'ThirdService'. Replace contract from 'ThirdService.IThirdService' to 'ThirdCommon.IThirdService'.
   • Select the ThirdService project as the startup project in the Solution Explorer and run it (Ctrl+F5).
     • Note that the WCF Service Host is automatically started by Visual Studio:
       
     • Also, the WCF Test Client application is automatically launched. This application can be used to test methods published by the service:
       
       In this tool a proper client configuration can also be viewed:
       
2. Create a client for the ThirdService.
   • Add to the solution a new Windows Forms Application project.
   • Add a ComboBox, a Button, and a DataGridView control to the form.
   • Add to the project a reference to the ThirdCommon project:
     
   • As a data source of the DataGridView control, choose the ThirdType class:
     
   • Add to the ComboBox control an item with address of the service, it can be found in the App.config file of the ThirdService project:
     <baseAddresses>
         <add baseAddress = "http://localhost:8731/Design_Time_Addresses/ThirdService/ThirdService/" />
     </baseAddresses>
   • Run the application to test if everything is OK:
     
   • Add to the project a service reference to the ThirdService:
     • Right click on the project and choose 'Add Service Reference'.
     • Click the 'Discover' button to try to find services in the current solution.
     • Use 'ThirdServiceReference' for the namespace:
       
   • 
   • Add the following code for the handler of the Click event of the button:
     private void callButton_Click(object sender, EventArgs e)
     {
         ThirdServiceReference.ThirdServiceClient client =
             new ThirdServiceReference.ThirdServiceClient();
     
         ThirdType third = client.GetThirdType("t1");
     
         thirdTypeBindingSource.Clear();
         thirdTypeBindingSource.Add(third);
     }
3. Test the client and the service.
   • Run the WCF Service Host application outside Visual Studio (using the wcfsvchost.exe tool) to host the ThirdService:
     Setting environment for using Microsoft Visual Studio 2008 x86 tools.
     
     C:\Program Files\Microsoft Visual Studio 9.0\VC>d:
     
     D:\>cd D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\ThirdService\bin\Debug\
     
     D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\ThirdService\bin\Debug>wcfsvchost.exe /service:ThirdService.dll /config:ThirdService.dll.config
     
     D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\ThirdService\bin\Debug>
   • Run the client application and click the Call button:
     
   • Check what happen when the service is not running:
     
4. Hosting in a managed application.
   • Add to the solution a new Console Application project (named ManagedAppHttpHost). This application will host our service using HTTP binding.
     
     • Add to the new project a reference to the System.ServiceModel assembly.
     • Add also references to the ThirdCommon and ThirdService projects.   
     • Add the following code to the Main method:
       static void Main(string[] args)
       {
           ServiceHost serviceHost = new ServiceHost(typeof(ThirdService.ThirdService));
       
           serviceHost.Open();
       
           Console.WriteLine("ManagedAppHttpHost - hosts the ThirdService using HTTP binding");
           Console.WriteLine("Press ENTER to finish hosting");
           Console.ReadLine();
       
           serviceHost.Close();
       }
       • To compile the code, make the ThirdService class in the ThirdService project public.
     • Add an 'Application Configuration File' item (App.config) to the project, with the following content:
       <?xml  version="1.0"  encoding="utf-8" ?>
       <configuration>
           <system.serviceModel>
               <services>
                   <service name="ThirdService.ThirdService"
                            behaviorConfiguration="ThirdServiceBehavior">
                       <host>
                           <baseAddresses>
                               <add baseAddress="http://localhost:2345/ThirdService"/>
                           </baseAddresses>
                       </host>
                       <endpoint address=""
                                 binding="basicHttpBinding"
                                 contract="ThirdCommon.IThirdService" />
                       <endpoint address="mex"
                                 binding="mexHttpBinding"
                                 contract="IMetadataExchange" />
                   </service>
               </services>
               <behaviors>
                   <serviceBehaviors>
                       <behavior name="ThirdServiceBehavior">
                           <serviceMetadata httpGetEnabled="true"/>
                       </behavior>
                   </serviceBehaviors>
               </behaviors>
           </system.serviceModel>
       </configuration>
     • Run the ManagedAppHttpHost project and test the host using a web browser and the specified in the configuration file address (http://localhost:2345/ThirdService):
       
   • Add a 'Service Reference' in the WinFormsClient project to the WCF service hosted at the specified address (be sure the ManagedAppHttpHost application is still running). Name the reference 'ManAppHttpServiceReference':
     
     • Take a look at the configuration file of the WinFormsClient project. The new service reference was added using the basicHttpBinding.
     • Modify the WinFormsClient project to allow to choose the target address (i.e. the target endpoint). Modify source code of the form:
       ServiceModelSectionGroup serviceModelConf = null;
       
       private void Form1_Load(object sender, EventArgs e)
       {
           addressComboBox.Items.Clear();
       
           serviceModelConf = ServiceModelSectionGroup.GetSectionGroup(
               ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.None));
           foreach (ChannelEndpointElement endpoint in serviceModelConf.Client.Endpoints)
           {
               addressComboBox.Items.Add(endpoint.Address);
           }
       
           addressComboBox.SelectedIndex = 0;
       }
       
       private void callButton_Click(object sender, EventArgs e)
       {
           thirdTypeBindingSource.Clear();
       
           ChannelFactory<ThirdCommon.IThirdService> channelFactory =
               new ChannelFactory<ThirdCommon.IThirdService>(
                   serviceModelConf.Client.Endpoints[addressComboBox.SelectedIndex].Name);
       
           IThirdService thirdService = channelFactory.CreateChannel();
           ThirdType third = thirdService.GetThirdType("t1");
       
           thirdTypeBindingSource.Add(third);
       }
       • The above code allows to list in the combobox all available endpoints and to create dynamically a target endpoint when there is a try to call the service's method.
     • Run the application and notice an error when try to connect to a properly running service:
       
     • The error is caused by using of other interface type than defined in the configuration of an endpoint. In the source code, the ThirdCommon.IThirdService is used, while in the configuration file the ThirdServiceReference.IThirdService and the ManAppHttpServiceReference.IThirdService resp. The solution is to modify names of types in the configuration file to ThirdCommon.IThirdService:
       <client>
           <endpoint address="http://localhost:8731/Design_Time_Addresses/ThirdService/ThirdService/"
               binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_IThirdService"
               contract="ThirdCommon.IThirdService" name="WSHttpBinding_IThirdService">
               <identity>
                   <dns value="localhost" />
               </identity>
           </endpoint>
           <endpoint address="http://localhost:2345/ThirdService" binding="basicHttpBinding"
               bindingConfiguration="BasicHttpBinding_IThirdService" contract="ThirdCommon.IThirdService"
               name="BasicHttpBinding_IThirdService" />
       </client>
     • Now, the application works:
       
5. Hosting in a Windows service.
   • Add to the solution a new Windows Service project, name it WindowsServiceNamedPipeHost:
     
     • Add references to the ThirdCommon and ThirdService projects.
     • Add a reference to the System.ServiceModel assembly.
     • Modify the service name used in the Service1.InitializeComponent method to WindowsServiceNamedPipeHost (it can also be done using the Properties window):
       private void InitializeComponent()
       {
           components = new System.ComponentModel.Container();
           this.ServiceName = "WindowsServiceNamedPipeHost";
       }
     • Add an installer for the Windows service (it can be easily done using the 'Add Installer' link from the Properties window):
       
       • The service installer is necessary to allow the Windows service to be installed in the system. It is just a class inherited from the Installer class with the RunInstallerAttribute applied.
     • Modify the content of the Service1.cs file to add the source code creating a WCF service host:
       public partial class Service1 : ServiceBase
       {
           public ServiceHost wcfServiceHost = null;
       
           public Service1()
           {
               InitializeComponent();
           }
       
           protected override void OnStart(string[] args)
           {
               if (wcfServiceHost != null)
               {
                   wcfServiceHost.Close();
               }
       
               wcfServiceHost = new ServiceHost(typeof(ThirdService.ThirdService));
               wcfServiceHost.Open();
           }
       
           protected override void OnStop()
           {
               if (wcfServiceHost != null)
               {
                   wcfServiceHost.Close();
                   wcfServiceHost = null;
               }
           }
       }
     • Add a configuration file to the project (App.config), and add a configuration of the hosted WCF service:
       <?xml version="1.0" encoding="utf-8" ?>
       <configuration>
           <system.serviceModel>
               <services>
                   <service name="ThirdService.ThirdService"
                            behaviorConfiguration="ThirdServiceBehavior">
                       <host>
                           <baseAddresses>
                               <add baseAddress="net.pipe://localhost/ThirdServiceByWinSrv"/>
                           </baseAddresses>
                       </host>
                       <endpoint address=""    
                                 contract="ThirdCommon.IThirdService"
                                 binding="netNamedPipeBinding" />
                       <endpoint address="mex"
                                 binding="mexNamedPipeBinding"
                                 contract="IMetadataExchange" />
                   </service>
               </services>
               <behaviors>
                   <serviceBehaviors>
                       <behavior name="ThirdServiceBehavior">
                           <serviceMetadata />
                       </behavior>
                   </serviceBehaviors>
               </behaviors>
           </system.serviceModel>
       </configuration>
       • Note that the netNamedPipeBinding is used. This binding allows for very efficient communication with WCF services but it is limited to a single system (both the service and the client must run on the same system).
       • Note that special mexNamedPipeBinding is used to allow the WCF service to be discovered.
   • Start hosting using the Windows service:
     • Compile the WindowsServiceNamedPipeHost project.
     • According to the message displayed after a try to run the service's executable, the service must be installed and run in a special way.
       
     • Install the Windows service:
       installutil WindowsServiceNamedPipeHost.exe
     • Provide a login (full login, including the machine's name: machine\login) and a password of a user installing the Windows service (usually, the user installing the service must be an administrator):
       
     • See the installation result on the console:
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>installutil WindowsServiceNamedPipeHost.exe
       Microsoft (R) .NET Framework Installation utility Version 2.0.50727.3053
       Copyright (c) Microsoft Corporation. All rights reserved.
       
       
       Running a transacted installation.
       
       Beginning the Install phase of the installation.
       See the contents of the log file for the D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe assembly's progress.
       The file is located at D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.InstallLog.
       Installing assembly 'D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe'.
       Affected parameters are:
       logtoconsole =
       assemblypath = D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe
       logfile = D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.InstallLog
       Installing service WindowsServiceNamedPipeHost...
       Service WindowsServiceNamedPipeHost has been successfully installed.
       Creating EventLog source WindowsServiceNamedPipeHost in log Application...
       
       The Install phase completed successfully, and the Commit phase is beginning.
       See the contents of the log file for the D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe assembly's progress.
       The file is located at D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.InstallLog.
       Committing assembly 'D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe'.
       Affected parameters are:
       logtoconsole =
       assemblypath = D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe
       logfile = D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.InstallLog
       
       The Commit phase completed successfully.
       
       The transacted install has completed.
       
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>
     • Check the list of all services installed in the system and find the WindowsServiceNamedPipeHost:
       
     • Run the service (using an option in the Services window or from the console):
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>net start WindowsServiceNamedPipeHost
       The WindowsServiceNamedPipeHost service is starting.
       The WindowsServiceNamedPipeHost service was started successfully.
       
       
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>
     • To test if the WCF service is hosted properly, the WCF Test Client tool (wcftesthost.exe) can be used:
       
   • Configure the WinFormsClient project to use the ThirdService hosted by a Windows service:
     • Add a 'Service Reference' to the WCF service hosted at address: net.pipe://localhost/ThirdServiceByWinSrv. Name it WinSrvNamedPipeServiceReference:
       
     • Modify the contract attribute of the endpoint node for the new service reference to value 'ThirdCommon.IThirdService'.
     • Run the WinFormsClient appplication to test if it works:
       
   • Test what happens if the host's configuration is wrong:
     • Stop the Windows service.
     • Break the WindowsServiceNamedPipeHost project's configuration file, e.g. by replacing the 'net.pipe://' prefix in the WCF service's address to 'http://'.
     • Build the project.
     • Try to start the Windows service:
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>net start WindowsServiceNamedPipeHost
       The WindowsServiceNamedPipeHost service is starting.
       The WindowsServiceNamedPipeHost service could not be started.
       
       The service did not report an error.
       
       More help is available by typing NET HELPMSG 3534.
       
       
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>
     • The service could not start. Because there is no error logging code in the service's source code, the only way to see the error is to use the EventViewer administrative tool:
       
     • To uinstall the Windows service, run the installutil \u command:
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>net stop WindowsServiceNamedPipeHost
       The WindowsServiceNamedPipeHost service is stopping.
       The WindowsServiceNamedPipeHost service was stopped successfully.
       
       
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>installutil /u WindowsServiceNamedPipeHost.exe
       Microsoft (R) .NET Framework Installation utility Version 2.0.50727.3053
       Copyright (c) Microsoft Corporation. All rights reserved.
       
       
       
       The uninstall is beginning.
       See the contents of the log file for the D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe assembly's progress.
       The file is located at D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.InstallLog.
       Uninstalling assembly 'D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe'.
       Affected parameters are:
       logtoconsole =
       assemblypath = D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.exe
       logfile = D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug\WindowsServiceNamedPipeHost.InstallLog
       Removing EventLog source WindowsServiceNamedPipeHost.
       Service WindowsServiceNamedPipeHost is being removed from the system...
       Service WindowsServiceNamedPipeHost was successfully removed from the system.
       
       The uninstall has completed.
       
       D:\PW\przedmioty\PwSW2\Tutorials\wcf\3.5\Advanced\Third\WindowsServiceNamedPipeHost\bin\Debug>
6. Hosting in IIS (Internet Information Services).
   • Add to the solution a new 'WCF Service Application' project. Name it IISHost:
     
     • Add to the project references to the ThirdCommon and ThirdService projects.
     • Remove the IService1.cs and the Service1.svc.cs files.
     • Rename the IService1.svc file to ThirdService.svc.
     • Modify the content of the ThirdService.svc file to:
       <%@ ServiceHost Language="C#" Debug="true" Service="ThirdService.ThirdService"%>
     • Modify the system.serviceModel node in the Web.config file to the following:
       <system.serviceModel>
         <services>
           <service name="ThirdService.ThirdService" behaviorConfiguration="IISHost.Service1Behavior">
             <!-- Service Endpoints -->
             <endpoint address="" binding="wsHttpBinding" contract="ThirdCommon.IThirdService">
               <!--
                   Upon deployment, the following identity element should be removed or replaced to reflect the
                   identity under which the deployed service runs.  If removed, WCF will infer an appropriate identity
                   automatically.
               -->
               <identity>
                 <dns value="localhost"/>
               </identity>
             </endpoint>
             <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
           </service>
         </services>
         <behaviors>
           <serviceBehaviors>
             <behavior name="IISHost.Service1Behavior">
               <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
               <serviceMetadata httpGetEnabled="true"/>
               <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
               <serviceDebug includeExceptionDetailInFaults="false"/>
             </behavior>
           </serviceBehaviors>
         </behaviors>
       </system.serviceModel>
     • Compile and run the project.
     • Test in a web browser the address: http://localhost:50836/ThirdService.svc (port number may vary):
       
   • Host the service in IIS:
     • Modify the properties of the IISHost project to use the IIS Web Server:
       
     • Be sure to create the virtual directory.
     • Test in a web browser the address: http://localhost/IISHost/ThirdService.svc:
       
     • Check the configuration in the IIS Manager:
       
     • To modify configuration of the hosted WCF service in other way than changing the Web.config file manually, the Service Configuration Editor can be used. Right click the Web.config file in the Solution Explorer window in Visual Studio and choose the 'Edit WCF Configuration' item:
       
   • Configure the WinFormsClient project to communicate with the WCF service hosted by IIS:
     • Add a service reference:
       
     • Modify the name of the contract in the Web.config file to ThirdCommon.IThirdService. Note that the localhost is changed to the name of the machine.
     • Run and test the application and the service:
       
7. Hosting in WAS (Windows Process Activation Service).
   • Windows Vista prerequisitives.
     • We will try to host our WCF service using WAS and the netTcpBinding. To allow this, the 'Windows Communication Foundation Non-HTTP Activation' option in the 'Windows Features' must be installed. By default, it is not installed:
       
     • To use a non-HTTP protocol, the site binding must be added to the WAS configuration.
       • Execute as an administrator in the console:
         C:\Windows\System32\inetsrv>appcmd.exe set site "Default Web Site" -+bindings.[protocol='net.tcp',bindingInformation='808:*']
         SITE object "Default Web Site" changed
         
         C:\Windows\System32\inetsrv>
   • Add to the solution a new 'WCF Service Application' project (hosting the WCF service using WAS will be configured in IIS as a normal web application):
     
     • Add references to the ThirdCommon and ThirdService projects.
     • Remove the IService1.cs and Service1.svc.cs files.
     • Rename the Service1.svc file to ThirdService.svc and modify its content to:
       <%@ ServiceHost Language="C#" Debug="true" Service="ThirdService.ThirdService"%>
     • Modify in the Web.config file configuration of the system.serviceModel node:
       <system.serviceModel>
       
           <services>
               <service name="ThirdService.ThirdService"
                        behaviorConfiguration="ThirdServiceBehavior">
                   <!-- This endpoint is exposed at the base address provided by host: net.tcp://localhost/WASHost/service.svc  -->
                   <endpoint binding="netTcpBinding" bindingConfiguration="PortSharingBinding"
                             contract="ThirdCommon.IThirdService" />
                   <!-- the mex endpoint is explosed at net.tcp://localhost/WASHost/service.svc/mex -->
                   <endpoint address="mex"
                             binding="mexTcpBinding"
                             contract="IMetadataExchange" />
               </service>
           </services>
           <bindings>
               <netTcpBinding>
                   <binding name="PortSharingBinding" portSharingEnabled="true">
                       <security mode="None" />
                   </binding>
               </netTcpBinding>
           </bindings>
       
           <!--For debugging purposes set the includeExceptionDetailInFaults attribute to true-->
           <behaviors>
               <serviceBehaviors>
                   <behavior name="ThirdServiceBehavior">
                       <serviceMetadata />
                       <serviceDebug includeExceptionDetailInFaults="False" />
                   </behavior>
               </serviceBehaviors>
           </behaviors>
       
       </system.serviceModel>
   • Set the application in the IIS configuration. As in the previous example, it can be done by the project's properties:
     
     • By default, only the HTTP protocol is enabled for applications hosted in IIS. To change it, use the appcmd.exe tool:
       C:\Windows\System32\inetsrv>appcmd.exe set app "Default Web Site/WASHost" /enabledProtocols:net.tcp
       APP object "Default Web Site/WASHost" changed
       
       C:\Windows\System32\inetsrv>
     • Test the new address (net.tcp://localhost/WASHost/ThirdService.svc) using the wcftestclient.exe tool:
       
   • As in previous examples, configure the WinFormsClient project to use the WCF service hosted using the netTcpBinding:
     
     
8. Tracing and message logging.
   • Tracing is used to record the flow and individual actions of the various components of a distributed application).
     • Configure the client to trace WCF communication.
       • Add to the App.config file the following configuration of tracing:
         <system.diagnostics>
             <sources>
                 <source name="System.ServiceModel"
                         propagateActivity="true"
                         switchValue="Warning,ActivityTracing">
                     <listeners>
                         <add type="System.Diagnostics.DefaultTraceListener"
                              name="Default">
                             <filter type=""/>
                         </add>
                         <add initializeData="Trace.log"
                              type="System.Diagnostics.XmlWriterTraceListener"
                              name="tracelog"
                              traceOutputOptions="Timestamp" >
                             <filter type=""/>
                         </add>
                     </listeners>
                 </source>
             </sources>
         </system.diagnostics>
       • Run the application, make some calls of service's methods, stop the application, and take a look at the Trace.log file:
         <E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
             <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
                 <EventID>131085</EventID>
                 <Type>3</Type>
                 <SubType Name="Start">0</SubType>
                 <Level>255</Level>
                 <TimeCreated SystemTime="2008-12-15T13:17:59.8865527Z" />
                 <Source Name="System.ServiceModel" />
                 <Correlation ActivityID="{c2b0bd6d-0348-43fe-b389-82d0803fb8ac}" />
                 <Execution ProcessName="WinFormsClient" ProcessID="14180" ThreadID="1" />
                 <Channel/>
                 <Computer>KMOSSAKOWSKI</Computer>
             </System>
             <ApplicationData>
                 <TraceData>
                     <DataItem>
                         <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Start">
                             <TraceIdentifier>http://msdn.microsoft.com/pl-PL/library/System.ServiceModel.Diagnostics.ActivityBoundary.aspx</TraceIdentifier>
                             <Description>Activity boundary.</Description>
                             <AppDomain>WinFormsClient.exe</AppDomain>
                             <ExtendedData xmlns="http://schemas.microsoft.com/2006/08/ServiceModel/DictionaryTraceRecord">
                                 <ActivityName>Process action 'http://tempuri.org/IThirdService/GetThirdType'.</ActivityName>
                                 <ActivityType>ProcessAction</ActivityType>
                             </ExtendedData>
                         </TraceRecord>
                     </DataItem>
                 </TraceData>
             </ApplicationData>
         </E2ETraceEvent>
   • Message logging is used to record the contents of the messages.
     • Modify configuration of the client:
       <system.diagnostics>
           <sources>
               <source name="System.ServiceModel.MessageLogging">
                   <listeners>
                       <add name="messages"
                            type="System.Diagnostics.TextWriterTraceListener"
                            initializeData="Messages.log" />
                   </listeners>
               </source>
           </sources>
       </system.diagnostics>
       
       <system.serviceModel>
           <diagnostics>
               <messageLogging logEntireMessage="true"
                               logMessagesAtServiceLevel="true" />
           </diagnostics>
       </system.serviceModel>
     • Take a look at the output Messages.log file:
       System.ServiceModel.MessageLogging Information: 0 : <MessageLogTraceRecord Time="2008-12-15T14:35:46.2835527+01:00" Source="ServiceLevelSendRequest" Type="System.ServiceModel.Dispatcher.OperationFormatter+OperationFormatterMessage" xmlns="http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace">
           <s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope">
               <s:Header>
                   <a:Action s:mustUnderstand="1">http://tempuri.org/IThirdService/GetThirdType</a:Action>
                   <a:MessageID>urn:uuid:6f9f4bed-1946-40c3-bb84-9a06bb4fdc27</a:MessageID>
                   <ActivityId CorrelationId="98029069-9b50-4648-9e5e-3e0e4c348aa8" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">2b55322c-3f21-41db-a0dd-9196ea06f6e1</ActivityId>
                   <a:ReplyTo>
                       <a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
                   </a:ReplyTo>
               </s:Header>
               <s:Body>
                   <GetThirdType xmlns="http://tempuri.org/">
                       <s>t1</s>
                   </GetThirdType>
               </s:Body>
           </s:Envelope>
       </MessageLogTraceRecord>
       System.ServiceModel.MessageLogging Information: 0 : <MessageLogTraceRecord Time="2008-12-15T14:35:47.9455527+01:00" Source="ServiceLevelReceiveReply" Type="System.ServiceModel.Channels.MessagePatterns+PatternMessage" xmlns="http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace">
           <s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope">
               <s:Header>
                   <a:Action s:mustUnderstand="1">http://tempuri.org/IThirdService/GetThirdTypeResponse</a:Action>
                   <a:RelatesTo>urn:uuid:6f9f4bed-1946-40c3-bb84-9a06bb4fdc27</a:RelatesTo>
                   <a:To s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/anonymous</a:To>
               </s:Header>
               <s:Body>
                   <GetThirdTypeResponse xmlns="http://tempuri.org/">
                       <GetThirdTypeResult xmlns:b="http://tempuri.org" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
                           <b:DateTimeValue>2008-12-15T14:35:47.9445527+01:00</b:DateTimeValue>
                           <b:IntValue>2</b:IntValue>
                           <b:StringValue>t1_modified</b:StringValue>
                       </GetThirdTypeResult>
                   </GetThirdTypeResponse>
               </s:Body>
           </s:Envelope>
       </MessageLogTraceRecord>
   • The Service Trace Viewer from Microsoft Windows SDK can be used to easily browse content of log files (but only the XmlWriterTraceListener is supported, so to see browse logs using the tool, don't use the TextWriterTraceListener in the above configuration):
     

[Source code]