WCF Service FAQs - Part 2

Submit Blog | Blogs Home |

This WCF Tutorial is part-2 in series of WCF Service FAQs. Previous part in this series is already published at WCF Service FAQs - Part 1.

What are the different ways to expose WCF Metadata?
By default, WCF doesn't expose metadata. We can expose it by choosing one of the following ways:

1.       In configuration file, by enabling metadata exchange as follows:

   <system.serviceModel>
       <services>
          <service name="MyService.Service1"
                  behaviorConfiguration="MyService.Service1">

                   <endpoint address="" binding="wsHttpBinding"
                              contract="MyService.IService1">

                                <identity>
                                    <dns value="localhost"/>
                                </identity>
</endpoint>
<endpoint address="mex" binding="mexHttpBinding"
           contract="IMetadataExchange"/>

          </service>
</services>
<behaviors>
          <serviceBehaviors>
                    <behavior name="MyService.Service1">
                                    <serviceMetadata httpGetEnabled="true"/>
                             <serviceDebug includeExceptionDetailInFaults="false"/>                  

                     </behavior>
           </serviceBehaviors>
</behaviors>
</system.serviceModel>

 
2.       ServiceHost can expose a metadata exchange endpoint to access metadata at runtime.

using (ServiceHost host = new ServiceHost(typeof(MyService)))
{
         ServiceMetadataBehavior behavior = new ServiceMetadataBehavior();
         behavior.HttpGetEnabled = true;
         host.Description.Behaviors.Add(behavior);
         host.Open();
         Console.WriteLine("My Service here..........");

         Console.ReadLine();
         host.Close();
}

What is mexHttpBinding in WCF?  
In order to generate proxy, we need service metadata and mexHttpBinding returns service metadata.

If we look into our configuration file, service will have an endpoint with mexHttpBinding as follows:
         <endpoint address="mex" binding="mexHttpBinding"   contract="IMetadataExchange"/>

and service metadata behavior will be configured as follows:

        <serviceMetadata httpGetEnabled="true"/>

Before deployment of application to production machine, it should be disabled.
In order to support other protocols, related bindings are mexHttpBinding, mexHttpsBinding, mexTcpBinding.

What is a Service Proxy in WCF?
A service proxy or simply proxy in WCF enables application(s) to interact with WCF Service by sending and receiving messages. It's basically a class that encapsulates service details i.e. service path, service implementation technology, platform and communication protocol etc. It contains all the methods of service contract (signature only, not the implementation). So, when the application interact the service through proxy, it gives the impression that it's communicating a local object.
We can create proxy for a service by using Visual Studio or SvcUtil.exe.


What are the different ways to generate proxy in WCF?
Generating proxy using Visual Studio is simple and straight forward.
      i) Right click References and choose "Add Service Reference".
      ii) Provide base address of the service on "Add Service Reference" dialog box and click "Go" button.
          Service will be listed below.
      iii) Provide namespace and click OK.
Visual studio will generate a proxy automatically.

We can generate proxy using svcutil.exe utility using command line. This utility requires few parameters like HTTP-GET address or the metadata exchange endpoint address and a proxy filename i.e. optional.
       svcutil http://localhost/MyService/Service1.svc /out:MyServiceProxy.cs

If we are hosting the service at a different port(other than default for IIS which is 80), we need to provide port number in base address.
       svcutil http://localhost:8080/MyService/Service1.svc /out:MyServiceProxy.cs

For parameter details regarding svcutil, please follow the MSDN link
http://msdn.microsoft.com/en-us/library/aa347733.aspx

Difference between using ChannelFactory and Proxies in WCF?
If we have control over Server and Client, then ChannelFactory is a good option because it relies on having local interfaces that actually describes the service i.e. service contract.

On the other hand, If we don't have control over server and only have WSDL/URL, then it's better to generate proxy using Visual Studio or SvcUtil. 
SvcUtil is better option as compared to Visual Studio because we have more control in case of SvcUtil.


How to create proxy for Non-WCF Services?

In case of Non-WCF Services, we can create proxy by either using Visual Studio or svcUtil.exe tool by pointing to WSDL of the non-WCF service. In this scenario, we can't create proxy through ChannelFactory or manually developing proxy class because we don't have local interfaces i.e. service contract.

Breifly explain Automatic Activation in WCF?

Automatic activation means service starts and serves the request when a message request is received, but service doesn't need to be running in advance.
There are few scenarios in which service needs to be running in advance, For example, in case of Self-Hosting.

What are the different WCF Instance Activation Methods available?

WCF supports three different types of Instance Activation methods

1. Per Call
2. Per Session
3. Singleton

For details on WCF Instance Activation Methods, please refer other article "WCF Interview Questions".

What are the different ways to handle concurrency in WCF?

There are three different ways to handle concurrency in WCF that are:

a)      Single

b)      Multiple

c)       Reentrant

Single: means at a given time, only a single request can be processed by WCF service instance. Other requests will be waiting until the first one is fully served.

Multiple: means multiple requests can be served by multiple threads of a single WCF service instance.

Reentrant: means a single WCF service instance can process one request at a given time but the thread can exit the service to call another service.

We can apply these concurrency settings by putting ConcurrencyMode property in ServiceBehavior as follows:

 [ServiceBehavior(ConcurrencyMode = ConcurrencyMode.Multiple]
Public class MyService : IMyService
{
}

What is WCF throttling?

WCF throttling enables us to regulate the maximum number of WCF instances, concurrent calls and concurrent sessions. Basic purpose is to control our WCF service performance by using Service throttling behavior.

In configuration file we can set this behavior as follows:

<serviceBehavior>
       <behavior name="MyServiceBehavior">
              <serviceThrottling
                              maxConcurrentInstances="2147483647"
                              maxConcurrentCalls="16"
                              maxConcurrentSessions="10"
       </behavior>
</serviceBehavior>

Above given values are the default ones, but we can update it after looking into the requirements of our application.

• WCF - Top 10 Interview Questions
• WCF Vs ASMX Web Services
• Understanding WCF Bindings and Channel Stack
• Simple Steps to enable tracing in WCF