wcf-binding

I have a the following server side app.config for a WCF service: <system.serviceModel> <bindings> <wsHttpBinding> <binding name="default" maxReceivedMessageSize="5000000"> <readerQuotas maxStringContentLength="5000000" maxArrayLength="5000000" /> </binding> </wsHttpBinding> </bindings> <services> <service behaviorConfiguration="Core.TOAService.Service1Behavior" name="Core.TOAService.TOAService"> <endpoint address="" binding="wsHttpBinding" contract="Core.TOAService.ITOAService"> <identity> <dns value="localhost" /> </identity> </endpoint> <endpoint address="mex" binding="mexHttpBinding"

When I try to call a WCF service I am getting the following message "An error occurred when verifying security for the message." When I remove the custom authenication the service works no problem. I can't figure out though what I have misconfigured in my web.config. Any insight would be appreciated. <system.serviceModel> <services> <service behaviorConfiguration="NAThriveExtensions.nableAPIBehavior" name="NAThriveExtensions.nableAPI"> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="basicHttpBinding_Secure" contract="NAThriveExtensions.InableAPI"> </endpoint> <endpoint

I am confused with Metadata publish concept. If in a WCF Service config file I had written : <serviceMetadata httpGetEnabled="false"/> No matter it is true or false. When I tried to give service reference in a client application using "Add Service Reference..." and clicked on "Discover", I am able to retrieve Service Reference. But when removed the following two lines: - <endpoint address="mex" binding="mexBasicHttpBinding" contract="IMetadataExchange"/> <serviceMetadata httpGetEnabled="false"/> Now after that when I tried to give reference in a client application using "Add Service Reference.

Okay, I must be missing something utterly simple here, because I've been googling for days, and looking at dozens of answers there, and here on SO, and i just CANNOT get this to work, no matter what i've tried. The service works perfectly fine when called over plain HTTP. Here's our setup... we have a domain, http://www.mydomain.com . We have an SSL certificate installed on that domain from thawte, just as we would if we were securing an e-commerce site. That all works fine, and i can go to http s ://www.mydomain.com and it works right. I'm running VS2008, .NET 3.5 site on Windows Server 2003

I'm writing a service that will only get calls from the local host. Performance is important so I thought I'd try the NetNamedPipeBinding instead of NetTcpBinding and see If I could see any noticeable performance gains. If a client, after having performed one or more requests to the server, is idle for a longer period of time the next request will fail seemingly due to some idle timeout in the binding. The same thing also happens when the service gets restarted. I need my clients to be able to keep a connection open for as long as it's allowed in order to avoid the overhead associated with

I can't seem to get my WCF service to accept large amounts of data being sent up to it. I configured the maxReceivedMessageSize for the client and could receive large data down just fine, that's not the issue. It's sending data up to the service. I tried to configure the service but haven't had any luck. Here's my web.config: <?xml version="1.0"?> <configuration> <system.web> <compilation debug="true"/> </system.web> <system.serviceModel> <behaviors> <serviceBehaviors> <behavior> <serviceMetadata httpGetEnabled="true"/> <serviceDebug includeExceptionDetailInFaults="false" /> <serviceDiscovery

I'm new to WCF and would like to know the differences/advantages/limitations/etc of each of the following bindings: net.pipe net.tcp http Supporting scenarios on when to use each binding and other examples would be appreciated. Joe Doyle While not great for providing specific usage examples, here is a link from MSDN which lists all the features for the bindings. http://msdn.microsoft.com/en-us/library/ms730879.aspx Here is a decent flow chart that can help choosing between them as well. Source: http://bloggingabout.net/blogs/dennis/archive/2006/12/01/WCF-Binding-decision-chart.aspx Here is a