Problem:

When you develop a WCF/Workflow service using Visual Studio and try to run it, by default Visual Studio runs it under web development server. Here the problem is that the web development server is a light weight host and does not support reach features which comes with IIS. For example web development server does not allow you to run a WCF/Workflow service, which is configured to use NET TCP binding. There are many more such features which do not come with web development server.

As a developer we all want to, just hit the F5 button and start debugging. But if your WCF/Workflow service is configured in such a way that it can only run under IIS, it becomes really tricky to start debugging it.

The common approach we generally follow is to out in which w3wp.exe our service is running and then attach the Visual Studio to that process.

In following text, I have shown another approach in which Visual Studio can be configured to run together with IIS. With this configuration your WCF/Workflow Services runs under IIS as soon you hit the F5 and you can start debugging without any hassles.

1.       Create WCF/Workflow server. See how to create basic Workflow WCF Server.

2.       Configure IIS to host your WCF/Workflow service.

(Note: -You can skip following steps if you already have some IIS website configured on port 80 and NET

TCP binding is configured. )

a.       Open IIS Manager.

b.      Add new application pool.

                                       i.      Select 'Application Pools' node from the left hand side tree view.

                                     ii.      Click on 'Add Application Pool' link from 'Actions' panel at right hand side.

                                    iii.      Give some name to your application pool. I have given name as 'WorkflowService'. In below steps I will refer your application pool as 'WorkflowService'.

                                   iv.      Change .Net Framework Version to 4.0

                                     v.      Click 'Ok'

c.       Add new 'Web Site Application' for your services.

                                       i.      Select 'Sites' node from the left hand side tree view.

                                     ii.      Right click on 'Sites' node and click 'Add Web Site'

                                    iii.      Give Some name to your Web Site. I have given name as 'WorkflowService'. I have given name as 'WorkflowService'. In below steps I will refer your website as 'WorkflowService'.

                                   iv.      Change Application Pool name to 'WorkflowService'.

                                     v.      Provide some directory path to create IIS virtual directory for this new web site.

                                   vi.      Provide host name as 'localhost'

                                  vii.      Click 'Ok'

 (Note : While clicking on Ok button you might get a message saying that some other website is already configured to run on port number 80. You just need to close that website and start your newly created website.) 

d.      Configure NET TCP Binding

                                       i.      Right click on 'WorkflowService ' web site and click on 'Edit Bindings' to open 'Site Bindings' dialog.

                                     ii.      Click on 'Add' button to open  'Add Site Binding' dialog.

                                    iii.      From 'Type' dropdown select 'net.tcp'.

                                   iv.      Type 808:* in Binding Information text box.

                                     v.      Click Ok.

e.      Enable NET TCP Binding on Web Site.

                                       i.      Select 'WorkflowService' website node from left hand side tree view.

                                     ii.      Click on 'Advanced Settings' from 'Actions' panel at right hand side.

                                    iii.      Update 'Enabled Protocols' field by adding comma delimited value as 'net.tcp' at the end of the existing value.

                                   iv.      Click 'Ok'

3.       Configure Visual Studio Project settings to use IIS as service host instead of default web development server.

a.       Select your service project in Solution Explorer and press ALT+ENTER to open project properties dialog.

b.      Click on 'Web' tab on project properties dialog.

c.       On 'Web' tab page, select 'Use local IIS Web Server' radio button.

d.      Click on 'Create Virtual Directory' button to link your website project with IIS.

(Note: This step will fail if Visual Studio is not running in Administrator privileges.) 

At this stage you have successfully configured IIS and Visual Studio to work together and help you debugging your WCF/Workflow services by just hitting on F5 button on Visual Studio.

To implement the above feature I was looking for the way to get execution control even before it goes to the service methods. Good news is that WCF itself helped me and gave the control with the help of it's extension points. Lets see what all extension points I used.

Proxy and Dispatcher

WCF works on messages which are send between client and service. Every time client wants to call a service  method, it sends a message to service with help of Proxy running in client process. Job of the Proxy is to take the client request and convert it into a message which is than further serialized and transferred to the service end. At service end this is received by Dispatcher. Dispatcher takes the message and desterilizes the content into appropriate CLR type, finds out which has to be called on behalf of the client and calls that message.

Both Proxy and Dispatcher provides many extension points using different interfaces. When you implement these interfaces in your own class and register those class with WCF framework (we will see how?), Both Proxy and Dispatcher calls the implementation in your class at the time of message processing.

Lets see what all interfaces are provided via WCF framework to intercept the message processing.

1. IParameterInspector : Called before and after invocation to inspect and modify parameter values.

1. IDispatchMessageFormatter/IClientFormatter : Called to perform serialization and deserialization.

1. IDispatchMessageInspector/IClientMessageInspector : Called before send or after receive to inspect and replace message contents.

1. IDispatchOperationSelector/IClientOperationSelector : Called to select the operation to invoke for the given message.

1. IOperationInvoker : Called to invoke the operation.

Registering your inspector class with WCF runtime

You use WCF behaviours to register your inspector classes with WCF runtime. When theServiceHost initializes the service, it looks into app.config/web.configfiles  for the behaviours to apply and also reflects over all the attributes applied on service contract methods to check if any attribute has implemented any behaviour interface. If it finds one, it creates an instance of that attribute type and calls appropriate methods of behaviour interface, implemented by attribute class, to you give you a change to register your interceptors during service initialization.  There are following types of behaviours provided supported in WCF

1. IServiceBehavior: Allows you to register your inspectors at Service level.

1. IEndpointBehavior: Allows you to register your inspectors at Endpoint level.

1. IContractBehavior: Allows you to register your inspectors at Service Contract level.

1. IOperarionBehavior: Allows you to register your inspectors at each Operation level.

All these behaviour interfaces are having same methods but the method signatures are different so that your only get those runtime objects which comes under the scope you want to extend. Following are the methods available in each behaviour interface.

1. Validate: Called just before the runtime is built—allows you to perform custom validation on the service description.

1. AddBindingParameters: Called in the first step of building the runtime, before the underlying channel is constructed—allows you to add parameters to influence the underlying channel stack.

1. ApplyClientBehavior: Allows behavior to inject proxy (client) inspectors. this method is not present on IServiceBehavior.

1. ApplyDispatchBehavior:Allows behavior to inject dispatcher inspectors. 

Now you know what all classes and interfaces are available from WCF to extend its runtime, lets extend the runtime to intercept the service method calls and log the entry and exit of method call automatically (without writing logging code in service method implementation).

Following are the classes involved in the example code. To make the sample as simple as possible I have create all these classes and interfaces in single WCF project without worrying about the modularization.

Code forLoggingAttribute.

Note how this class is inherited from Attribute class and implementing IOperationBehavior. Methods of IOperationBehavior will be called by ServiceHost at the time of service initialization process to give you a chance to register your inspectors. In this example I am registring LoggingInspector instance.

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.ServiceModel.Description;

namespaceSampleService

{

public class LoggingAttribute : Attribute, IOperationBehavior

{

        public voidAddBindingParameters(OperationDescription operationDescription, System.ServiceModel.Channels.BindingParameterCollection bindingParameters)

        {

            //for this example no implementation is required in this method.

        }

        public voidApplyClientBehavior(OperationDescription operationDescription, System.ServiceModel.Dispatcher.ClientOperation clientOperation)

        {

            //for this example no implementation is required in this method.

        }

 

        public voidApplyDispatchBehavior(OperationDescription operationDescription, System.ServiceModel.Dispatcher.DispatchOperation dispatchOperation)

        {

            //Register your inspector class

            dispatchOperation.ParameterInspectors.Add(new LoggingInspector());

        }

        public void Validate(OperationDescription operationDescription)

        {

            //for this example no implementation is required in this method.

        }

    }

}

Code forLoggingInspector:

Note: LoggingInspector is implementing IParameterInspector interface and providing the logging functionality.

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.ServiceModel.Dispatcher;

namespaceSampleService

{

    public class LoggingInspector :IParameterInspector

    {

        public void AfterCall(stringoperationName, object[] outputs, object returnValue, object correlationState)

        {

            //Your can put any logging code here. here is the dummy one.

            Console.WriteLine(string.Format("Method exit : {0}",operationName));

        }

        public object BeforeCall(stringoperationName, object[] inputs)

        {

            //Your can put any logging code here. here is the dummy one.

            Console.WriteLine(string.Format("Method entry : {0}",operationName));

            return null;

        }

    }

}

Code forISampleService service contract interface:

Here I am applying my own custom attribute to enable automatic logging on IncrementNumber method.

using System;

using System.Collections.Generic;

using System.Linq;

using System.Runtime.Serialization;

using System.ServiceModel;

using System.ServiceModel.Web;

using System.Text;

namespaceSampleService

{

    [ServiceContract]

    public interface ISampleService

    {

        [OperationContract]

        [Logging]

        int IncrementNumber(int number);

    }

}

Code forSampleService implementation:

Note: There is no logging related implementation inside IncrementNumber method implementation.

using System;

using System.Collections.Generic;

using System.Linq;

using System.Runtime.Serialization;

using System.ServiceModel;

using System.ServiceModel.Web;

using System.Text;

namespaceSampleService

{

    public class SampleService : ISampleService

    {

        public int IncrementNumber(int number)

        {

            return number++;

        }

    }

}