wcf-binding

I need to create WCF Application, which will be working with pictures. It allows you to get a picture as a stream, and to send a picture to server (as a stream). It will work in streaming transfer mode. At the moment I hesitate over this choise. BasicHttpBinding or NetTcpBinding? What differences are between them? Advantages and disadvantages. Which will be better for this problem? Check out this blog post (or many other, similar ones) The diagram to choose the proper binding is from Juval Lowy's book Programming WCF Services and gives the best guidance, really: Now your additional requirement

WCF binding chooser algorithm I have watched a speak at a TechEd conference that showed a simple algorithm for choosing a WCF binding. I can't find this algorithm but I remember some of the main ideas: If your WCF service will have non-.NET clients choose Http Soap If your WCF will have .NET clients in other machines choose Net Tcp If your WCF will have .NET clients in the same machine choose Message Queue Can anyone provide a link to the full version of this algorithm? marc_s Something like that maybe? WCF Binding Decision Chart WCF Binding Decision Chart http://img109.imageshack.us/img109

I've got a simple WCF service that has worked fine while I've been testing on my dev machine. Now I've moved the web service to a web server, and I'm running the service (in debug mode) at http://mydomain.com:8005 . Opening a web browser to that URL shows the expected service page, and if I put a breakpoint on the server inside the interface I'm calling, it hits the breakpoint and returns the expected data... but on the client side it comes back with the following error: An error occurred while receiving the HTTP response to http://mydomain.com:8005/ . This could be due to the service endpoint

I've been struggling for a few days with this problem , learning a lot of things on bindings in the process. One thing puzzles me, though: various links (see this or that for example) explicitly state "By default, WCF project is created using WsHttpBinding", but that's not what I see. This is what I do: Open Visual Studio 2010 and choose New Project / Visual C# / WCF Service Application Don't touch anything inside the code, set a local IIS Url for the service (say http://localhost/WcfService7 ) Open soapUI and choose File / New Soap UI Project / enter the url of the newly created wsdl: http:/

I have a WCF Service hosted as Windows Service and client is an ASP.Net application consuming WCF Service methods. In process of implementing security, I am confused over which among netTcpBinding / wsHttpBinding will be suitable for my case. Most likely all the applications in scene (WCF Service, Windows Service, ASP.Net Website) will be sitting on different servers in our office, thus in an Intranet. ASP.Net website will be accessed by users over Internet. Though, I can always use wsHttpBinding here, will it be suitable to set the service endpoint using netTcpBinding in my case? Justin

So I'm not overly familiar with WCF and all the stuff I've googled hasn't helped me with how to achieve what I need. Sorry if this is a dumb question :) Basically there is a server app with services exposed with WCF (net tcp binding). I've written a new console app and I need to call the service. So I can achieve this by adding a dll for the proxy project we have and by adding a bunch of config files (such as WCFClientBindings, WCFClientEndPoints). If I use a defined end point then I can call code like this: using (var partyProxy = new PartyControllerProxy()) { // execute server method

I need to integrate my server with non-WCF client and suggested to change SOAP version in the headers. This can be done with <textMessageEncoding messageVersion="Soap11" /> element on a custom binding so i need to convert my current basicHttpBinding . How can i do that? <basicHttpBinding> <binding> <security mode="TransportWithMessageCredential"> <transport clientCredentialType="Windows"/> <message clientCredentialType="UserName" /> </security> </binding> </basicHttpBinding> The custom binding definition is: <customBinding> <binding name="basicHttpEquivalent"> <security authenticationMode=