This WCF Tutorial is part 2 in a series of WCF Service FAQs. The previous part in this series is already published at WCF Service FAQs: Part 1.
What are the various ways to expose WCF Metadata?
By default, WCF doesn't expose metadata. We can expose it by choosing one of the following ways:
- In the configuration file, by enabling metadata exchange as follows:
<system.serviceModel>
<services>
<servicename="MyService.Service1"
behaviorConfiguration="MyService.Service1">
<endpointaddress=""binding="wsHttpBinding"
contract="MyService.IService1">
<identity>
<dnsvalue="localhost"/>
</identity>
</endpoint>
<endpointaddress="mex"binding="mexHttpBinding"
contract="IMetadataExchange"/>
</service>
</services>
<behaviors>
<serviceBehaviors>
<behaviorname="MyService.Service1">
<serviceMetadatahttpGetEnabled="true"/>
<serviceDebugincludeExceptionDetailInFaults="false"/>
</behavior>
</serviceBehaviors>
</behaviors>
</system.serviceModel>
- 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?
To generate a proxy, we need service metadata and mexHttpBinding returns service metadata.
If we look into our configuration file, the service will have an endpoint with mexHttpBinding as follows:
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
and the service metadata behavior will be configured as follows:
<serviceMetadata httpGetEnabled="true"/>
Before deployment of the application to a production machine, it should be disabled.
To support other protocols, related bindings are mexHttpBinding, mexHttpsBinding and mexTcpBinding.
What is a Service Proxy in WCF?
A service proxy or simply proxy in WCF enables application(s) to interact with a 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 a service contract (signature only, not the implementation). So, when the application interacts with the service through the proxy, it gives the impression that it's communicating a local object.
We can create a proxy for a service by using Visual Studio or the SvcUtil.exe.
What are the various ways to generate a proxy in WCF?
Generating a proxy using Visual Studio is simple and straight forward.
- Right-click References and choose "Add Service Reference".
- Provide the base address of the service on "Add Service Reference" dialog box and click the "Go" button.
The service will be listed below.
- Provide the namespace and click OK.
Visual Studio will generate a proxy automatically.
We can generate a proxy using the svcutil.exe utility using the command line. This utility requires a few parameters like HTTP-GET address or the metadata exchange endpoint address and a proxy filename i.e. optional. For example:
svcutil http://localhost/MyService/Service1.svc /out:MyServiceProxy.cs
If we are hosting the service at a different port (other than the default for IIS which is 80), we need to provide a port number in the base address. For example:
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
What is the difference between use of ChannelFactory and Proxies in WCF?
If we have control over the server and client, then the 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 the server and only have a WSDL/URL, then it's better to generate a proxy using Visual Studio or SvcUtil.
SvcUtil is a better option as compared to Visual Studio because we have more control using SvcUtil.
How to create proxy for Non-WCF Services?
In case of Non-WCF Services, we can create a proxy by either using Visual Studio or the svcUtil.exe tool by pointing to a WSDL of the non-WCF service. In this scenario, we can't create a proxy through a ChannelFactory or manually developing a proxy class because we don't have local interfaces i.e. a service contract.
Breifly explain Automatic Activation in WCF?
Automatic activation means the service starts and serves the request when a message request is received, but the service doesn't need to be running in advance.
There are a few scenarios in which the service needs to be running in advance. For example, in the case of Self-Hosting.
What are the various WCF Instance Activation Methods available?
WCF supports three different types of Instance Activation methods:
- Per Call
- Per Session
- Singleton
What are the various ways to handle concurrency in WCF?
There are three different ways to handle concurrency in WCF; they are:
- Single
- Multiple
- Reentrant
Single: at a given time, only a single request can be processed by a WCF service instance. Other requests will be waiting until the first one is fully served.
Multiple: multiple requests can be served by multiple threads of a single WCF service instance.
Reentrant: 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. The basic purpose is to control our WCF service performance by using Service throttling behavior.
In the configuration file we can set this behavior as follows:
<serviceBehavior>
<behavior name="MyServiceBehavior">
<serviceThrottling
maxConcurrentInstances="2147483647"
maxConcurrentCalls="16"
maxConcurrentSessions="10"
</behavior>
</serviceBehavior>
The above given values are the default ones, but we can modify them after evaluating the requirements of our application.