I was watching the webcas about WCF Deployment with Keith Elder and at around 30 minutes, he speaks about the "The collection already contains an address with scheme http" problem and explains that we must define a BaseAddressPrefixFilter in the web.config. The problem is that even with this, we're still forced to use only one host name.
Anyone has a solution if I have to support aliases for my web site?
In WCF 4.0 this has been completely addressed. You don't even need to bother with BaseAddressPrefixFilter. My suggestion, upgrade to .NET 4.0.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.