Using WCF on Windows Azure

Today, the WCF team released a patch that will help you if your are using WCF on Windows Azure

Essentially, if you use the "Add Service Reference..." feature in Visual Studio or svutil to generate WSDL for a service that is hosted on Windows Azure either locally or in the cloud, the WSDL would contain incorrect URIs. 

The problem has to do with the fact that in a load balanced scenario like Windows Azure, there are ports that are used internally (behind the load balancer) and ports that are used externally (i.e. internet facing).  The internal ports were showing up in the URIs.

Also note that this patch is not yet in the cloud, but will be soon. i.e. it will only help you in the Development Fabric scenario for now. (Will post when the patch is available in the cloud.)

While we're on the topic of patches, please see the list of patches related to Windows Azure.

Comments (2)

  1. Joannes Vermorel says:

    Any update about the patch being applied to Windows Azure? This news is about 6 months old, and we are still facing the problem. Will it be part of the .NET 4.0?

  2. Joannes — the patch is already in the Windows Azure VMs, are you seeing something different?

    .NET 4 does resolve this problem, the patch is in the runtime.

Skip to main content