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
Related
I have an old ASP.NET app connecting to a .NET Remoting service. I'd replaced the .NET Remoting service to a WCF service. I have the original WSDL and I've generated a WCF service by the help of svcutil. I don't know whether the client will able to connect and call the WCF service without changing its code.
Is it possible to solve this problem, please?
A service can be both a remoting service and a WCF service at the same time.
Just configure it with RemotingServices as usual for remoting.
Then decorate with OperationContract / ServiceContract and construct with ServiceHost and you can create clients for both techniques, just that remoting is TCP only.
WCF and Remoting are different paradigms. So if you changed your Remoting server to .NET WCF service, you will have to change the client code to use the wsdl generated client
look at https://learn.microsoft.com/en-us/dotnet/framework/wcf/migrating-from-net-remoting-to-wcf#Client_Comp. it should not be difficult
Hi
I have a SL4 application which uses a WCF service using net.tcp binding. If i remove http from the protocols of the service in IIS (Advanced settings ) and keep only net.tcp , the service fails with an error saying that the service could not be activated.
Does http need to be added to the proptocols of the service in IIS for the net.tcp to work?
i cannot enable http on IIS for the service protocols.
are there any workarounds
thanks
Ben
Which version of IIS are you using? Net.TCP will fail if you are not using IIS7 or when a butterfly flaps its wings in Tokyo.
Have you seen this blog post?
http://www.silverlightshow.net/items/WCF-NET.TCP-Protocol-in-Silverlight-4.aspx
issue resolved. was something very small that i had overlooked.
The mexhttp binding was present and the
httpGetEnabled was set in the service behaviors
removing the above resolved the issue
How can we consume WCF service in .Net 2.0 Winform. Please note that we don't have IIS on the client. an example or a sample would be great.
It all depends on how your WCF endpoints are configured.
If you're using SOAP based WCF Services over HTTP, you should be able to simply add a Service Reference from your .NET 2.0 WinForms application and be on your way (which is what I would suggest doing).
If that's not the case, you'll have to provide a little more detail about what you're trying to do with your WCF Services.
You can host your WCF service in a Windows Service as per this article. In that case, it will listen on the HTTP protocol on any port you configure.
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
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