Using WCF on Localhost on Azure

In summary How do I acces a WCF service on localhost when hosted in IIS on Azure? Azure does not bind localhost or to my website.

Details I have an ASP.Net application hosted on Azure. I have added a .svc and some workflows that I want to use via WCF. To keep matters simple, my web app simply calls the service on localhost, so I have endpoints like these in web.config;

  <endpoint address="http://localhost:8080/Router.svc/Case" binding="basicHttpBinding" contract="NewOrbit.ExVerifier.Model.Workflow.Case.ICaseWorkflow" name="Case" />
  <endpoint address="http://localhost:8080/Workflow/Case/Case_default1.xamlx" binding="basicHttpBinding" contract="*" name="Case_default1" />

This works just fine on my local machine. The problem is that when I publish this to Azure, the Website in IIS does not get a binding to localhost, instead the bindings are always to the actual IP address of the server. It ends up looking like this in applicationHost.config:

   <binding protocol="http" bindingInformation="" />
   <binding protocol="https" bindingInformation="" />
   <binding protocol="http" bindingInformation="" />

So, as soon as my web app tries to call the service on localhost (or for that matter) it fails instantly. Needless to say, if I rdp on to the server and change the binding then all is fine.

What I find really odd is that there are tons of examples out there where people are accessing WCF services on localhost on Azure so I can't figure out why this is so. I have set the osFamily to 2 and in order to debug this I have enabled web publishing and remote desktop access which I guess, in theory, could mess things up.

What I have already looked at

  • I can rewrite the end-point address in my code at runtime to substitute localhost for the actual address or create the endpoint dynamically as described by Ron in the answers. Unfortunately I am using the WCF Routing service so I can version workflows. This means that my code calls the Router endpoint and the WCF Router in turns calls the actual service/workflow using an endpoint specified in web.config. I don't have control over the Routing services endpoint resolution without, I think, writing a whole set of routing logic which just seems to be a lot of work when all I want is to call localhost :)
  • Switching to using named pipes; Alas, it causes some strange issues with workflows, probably due to duplexing, and I am on a deadline so haven't got time to get to the bottom of that at the minute.


You have to build the endpoint address dynamically.

Step 1: In your ServiceDefinition.csdef you need to declare an Endpoint.

<ServiceDefinition name="MyFirstAzureWorkflow" xmlns="">
  <WebRole name="WorkflowWeb" vmsize="ExtraSmall">
      <Site name="Web">
          <Binding name="Endpoint1" endpointName="WorkflowService" />
      <InputEndpoint name="WorkflowService" protocol="http" port="80" />
      <Import moduleName="Diagnostics" />

Step 2: When you want to call the service

var endpoint = RoleEnvironment.CurrentRoleInstance.InstanceEndpoints["WorkflowService"].IPEndpoint;
var uri = new Uri(string.Format(
var proxy = new ServiceClient(
    new BasicHttpBinding(),
    new EndpointAddress(uri));

Need Your Help

sed can not work in script file in Windows

windows sed

I once write a simple sed command like this

Prolog: inequality operator

prolog prolog-dif

I am using SICStus Prolog and have a set of facts:

About UNIX Resources Network

Original, collect and organize Developers related documents, information and materials, contains jQuery, Html, CSS, MySQL, .NET, ASP.NET, SQL, objective-c, iPhone, Ruby on Rails, C, SQL Server, Ruby, Arrays, Regex, ASP.NET MVC, WPF, XML, Ajax, DataBase, and so on.