Does silverlight 4 beta supports wshttpbinding (wcf)? If not, will it be supported in stable release?
No, it doesn't look like it. Check out these blog post on the topic:
New Web Services features in Silverlight 4 Beta
WCF net.tcp Protocol in Silverlight 4
Silverlight 4 will support the NetTcp Binding, mostly for intranet scenarios - but I haven't heard anything about support for wsHttpBinding, sorry.
Marc
Related
I have developed a self-hosted WPF server application and a client WPF application which communicated with WCF NetTcpBinding with duplex like common connected TCP socket communication scenario.
Now, I will develop a mobile client which communicates existing self-hosted WPF server application.
I know that old Xamarin does not support NetTcpBinding.
Does the latest Xamarin Forms (or Xamarin.Android, Xamarin.iOS) support NetTcpBinding with duplex? It seems that .NET Core 3.0 supports NetTcpBinding, but I have no idea for Xamarin.
If Xamarin does not support WCF NetTcpBinding, is self-hosted SignalR a good alternative for full duplex connected communication?
As far as I know, Dotnet Core3.0 SDK supports the Nettcpbinding and I can generate the client proxy class properly by using Microsoft WCF web service reference provider. Thereby it supports duplex communication too.
I didn’t have much exposure to Xamarin. If the project based on the Core 3.0 SDK. I think it should be capable of supporting Nettcpbinding.
Feel free to let me know if there is anything I can help with.
Does/Will MonoTouch support the new NetHttpBinding of WCF 4.5?
Thanks!
NetHttpBinding is a binding designed for consuming HTTP or WebSocket services. But it only uses WebSocket on Windows 8, otherwise it uses Http.
see: http://msdn.microsoft.com/en-us/library/system.servicemodel.nethttpbinding.aspx
Mono touch supports the same client bindings as silverlight 3 which means basichttpbinding. (atleast according to the latest info I have been able to find)
In your case since you are using xamarin, I assume that you are not running on Windows 8, therefore you are probably stuck with basichttpbinding.
I am facing a problem.
Please explain if this is possible or not.
1) I created a Service Library (.Net 3.5)
2) I created a Windows Service (.Net 3.5), added ServiceHost and implemented my ServiceLibrary to work as a TCP Endpoint.
3) Next I created a Console Client (.Net 3.5) and tried to get data from my TCP Endpoint…(svcutil….proxy.cs generation). Worked absolutely fine.
4) I have a Windows Client(.Net 1.1). How do I configure it to use this new Service? I can't add Proxy.cs as it says that servicemodel cannot be found…
You will need to use a basicHttpBinding, which is backward compatible and can be consumed by a .net 1.1 client. You should be able to find plenty of useful examples on the web: Consuming WCF with .Net 1.1 Basic Binding. For example, this Link describes that binding and usage of Soap 1.1 to make it compatible with .Net 1.1.
For more details on different scenarios and the range of wcf configuration possibilities, try exploring this CodePlex Link, specifically the Application Scenarios section that provides details of different setups. I believe that you will require a basicHttpBinding rather than a netTcpBinding in order to work with legacy protocols. The netTCPBinding would assume that you have .NET 3.0 at both ends. See this MSDN Bindings Link.
i have develop a silverlight application with wcf net.tcp binding. i want create an object of service in sliverlight. how it is possible. please help me.
Thanks
Version Update,
Silverlight 4 now has the net.tcp binding
No, as far as I know, up to and including Silverlight 3, it supports only the basicHttpBinding (and possibly the webHttpBinding as well?). NetTCP is not supported, sorry.
Here's a blog post by Yavor Georgiev (Program Manager, Silverlight Web Services Team) where he explains what's new in web services with Silverlight 3 - unfortunately, no mention of netTCP :-(
Marc
Silverlight 4 supports tcp binding.
Some extended info:
http://tomasz.janczuk.org/2009/11/wcf-nettcp-protocol-in-silverlight-4.html
For my project's web services I want to support desktop clients and silverlight clients. Should I write a separate web service for each or put all the operations in one service? If I put them all in one, I have to go with basicHttpBinding. The winforms app uses wsHttpBinding now, what do I lose going with basicHttpBinding?
I very strongly recommend you read this thoroughly:
"Silverlight and WCF Feature Comparison"
http://msdn.microsoft.com/en-us/library/cc896571(VS.95).aspx
There are quite a few gotchas when developing a web service for silverlight usage, especially if you already have a wsHttpBinding solution. Good luck!
EDIT: also I found this article useful:
WCF : BasicHttpBinding compared to WSHttpBinding at SOAP packet level
http://geekswithblogs.net/claeyskurt/archive/2008/04/22/121508.aspx
Use one web service with two endpoints, that would allow you to support basicHttpBinding as well as wsHttpBinding.
The difference between the two bindings is that basic is Soap 1.1 whereas ws is Soap 1.2 and WS-Addressing Specifications, in addition wsHttpBinding offers more security options