Supporting Multiple IIS Bindings Per Site
If you see this error when you are hosting in IIS then most probably you have multiple IIS bindings per scheme in your web site. WCF in .Net Framework 3.0 ,out of the box, does not support multiple binding per site, but this can enabled by extending the System.ServiceModel.Activation.ServiceHostFactory, and providing a CustomServiceHostFactory. CustomServiceHostFactory picks the appropriate base address for the application. The Factory attribute in the ServiceHost directive is set to the CustomSerivceHostFactory.
The only drawback is every developer hosting their application will need to change the svc file to provide the CustomServiceHostFactory, which picks the appropriate base address.
public class MultipleIISBindingSupportServiceHostFactory : ServiceHostFactory
{
protected override ServiceHost CreateServiceHost(Type serviceType, Uri[] baseAddresses)
{
Uri[] requiredAddress = GetAppropriateBase(baseAddresses);
return base.CreateServiceHost(serviceType, requiredAddress);
}
Uri[] GetAppropriateBase(Uri [] baseAddresses)
{
List<Uri> retAddress = new List<Uri>();
foreach (Uri address in baseAddresses)
{
if (address.DnsSafeHost == "localhost")
{
retAddress.Add(address);
}
}
return retAddress.ToArray();
}
}
In the svc file, fill in the Factory attribute
<%@ServiceHost Factory="NS.MultipleIISBindingSupportServiceHostFactory" Service="CalculatorService" %>
Anonymous
August 01, 2007
The comment has been removedAnonymous
February 11, 2008
Background IIS has web sites, which are containers for virtual applications which contain virtual directories.Anonymous
February 11, 2008
Background IIS has web sites, which are containers for virtual applications which contain virtual directoriesAnonymous
May 09, 2008
[WCF] This collection already contains an address with scheme http...Anonymous
August 14, 2008
Calling a WCF Service from Silverlight 2.0: Part TwoAnonymous
November 19, 2008
As a self-confessed crayon wielder I tend not to get involved in the washing machine technology of web