-
-
The default behavior of WCF Webservice is the new wsHttpBinding. This is not compatible with .NET 2.0, so to use it you must change the behavior with the basicHttpBinding.
The basic one is not secured, so if it’s a critical piece, you must use it with SSL.
-f.
ref.: http://www.slickit.ca/2009/04/wcf-using-wcf-with-net-20.html
-
-
When deploying a WCF service, this problem can occur
This collection already contains an address with scheme http. There can be at most one address per scheme in this collection.
Parameter name: item
This is caused by having multiple binding on the Website (like domain.com and www.domain.com).
The solution was simply to add a entry in the serviceHostingEnvironment section of the web.config, check out the reference for the complete solution.
warning: this cause the server to reject everything that is not configured in the baseAddressPrefixFilters.
-f.
ref.: http://blogs.msdn.com/rampo/archive/2008/02/11/how-can-wcf-support-multiple-iis-binding-specified-per-site.aspx
-
-
When deploying a .NET WCF Service on IIS 7, on might have a 404 error.
This is because the ScriptsMaps are not registered, issuing the following command register them, to that they can be used.
c:\Windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\servicemodelreg.exe –i
-f.
ref.: http://forums.asp.net/t/1432444.aspx