Reader Level:

Windows Azure for Developers Task 8: Working with WCF Service Web Role

By Dhananjay Kumar on Mar 22, 2011
In this article, we will create a WCF Service Role and host on local development fabric and consume in a console application.

WCF Service Role enables us to create a WCF service and host it in Windows Azure. In this article, we will create a WCF Service Role and host on local development fabric and consume in a console application. In the second part of this article we will move the WCF Service to an Azure portal.

To start with,

  1. Create a New Project
  2. Navigate to cloud tab
  3. Create Windows Azure Project
  4. Select WCF Service Role from given options.


If you look in the Solution Explorer, you will find in the WCF Service Role project the exact same structure and files as when a normal WCF Service Application is created. It contains:
  1. IService1.cs (Service Contract )
  2. Service1.svc.cs ( Service definition file )
  3. Web.config ( configuration for EndPoints)

We can modify these files accordingly for our purpose in exactly the same way that we usually do in a WCF Service Application.

Let us modify Service Contract as below:


using System.ServiceModel;
namespace WCFServiceWebRole1
    public interface IService1
        string GetData(int value);

And service definition would be:


namespace WCFServiceWebRole1

    public class Service1 : IService1
        public string GetData(int value)
            return string.Format("You entered: {0}", value);

Leave the default configuration in Web.Config.

Make sure you have set the Windows Azure project as the Startup project and run the application. In the browser you will get the error message shown below.


Ignore this message and append service.svc with URL, so the URL would be Service.svc is the name of the service definition. After appending you will get the usual WCF Service message in the browser.


To test this WCF Service role in a console client:
  1. Create a console application project
  2. Add Service Reference by providing URL


Now we will make a normal service call:


using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using ConsoleApplication14.ServiceReference1;

namespace ConsoleApplication14
    class Program
        static void Main(string[] args)
            Service1Client proxy = new Service1Client();
            var result = proxy.GetData(99);

Now when you run you may or may not get the exception shown below.


To solve the above exception, we have to edit App.Config file. We need to change:

WebRole6.gif to localhost. Because it might be that the console application is not able to resolve, we need to change it to localhost.


Now on running we will get the following output:


One behavior to be noticed here is that sometime you may get a time out exception after changing to localhost. In my further articles, I will drill down this unwanted behavior.

Dhananjay  Kumar
Dhananjay Kumar

Dhananjay kumar is 6 times Microsoft MVP, 7 times C# Corner MVP. He works as consultant for Infragistics in India. He is known for mentoring teams on various technologies.

Personal Blog: