i've been trying for a couple days making a duplex communication with a service present on WebRole in Azure. I add a reference of service to my client (console aplication running locally) and when try to call methods on service it never works.
If i try on azure emulator everything works fine.
Does anyone knows how to do that correctly? Where can i find tutorials with step by step works to do that ? I already made a lot of researches but any works or explains this.
Related
I need to host ASP.NET based app as Azure Web App which should communicate with WCF based Azure Web App. ( WCF app is also an azure Web App not an on-premise app at all).
What are possible ways to achieve easy and flexible communication between both app services?
Do we need to establish a communication channel specifically?
Both Apps under IIS On-Premises are used to communicate without any problem over NET TCP protocol. But I think now we need both services to communicate over HTTP instead of Net TCP?
What problems we may have?
What things do we need to bear in mind?
First of all, we need to be clear that azure webapp only supports ports 80 and 443.
Secondly, in your project, you said that it runs normally in local, because I don't know what you mean by communicate, and I don't know how to achieve it. Normal communication may be socket or websocket, etc. It is not clear what communication you are talking about. If it is socket and you need to use a port other than 443/80, then it is not supported.
But I know clearly that azure web app supports wcf, which means that both of your webapps can be deployed successfully and run normally. If there is a problem, you can update the error details in the post, and we can provide you with further assistance.
I am trying to create a chat application in WCF.
I've created the client and the service on a localhost using httpBinding,
this is the service endpoint:
http://localhost:9999/ProductService
Now, I really don't know how to make the program run 'globaly' and not on a localhost.
Is there anyway to host the server on my pc? or run the application serverless using p2p communications?
Thanks anyway for your Time
You can set up at publicly accessible web server on your own computer, but it's definitely not recommended for any production purposes, unless you have a good understanding of this and have a internet-connection that allows for it, both technically and legally.
You should probably get external web hosting for this instead.
But if you really want to do this, you can install IIS to host the service.
As a side note, I don't think WCF is the optimal route to take for this anymore. Maybee you should check out SignalR and/or WebSockets instead. And ASP.NET Core WebAPI. It's not really anything wrong with WCF, but for new projects I wouldn't recommend it.
I have developed a WCF service and hosted in IIS, I need that this service can be consumed by web applications and for one desktop application, but this desktop application was made in .net 2.0, so i add an asmx extension in order to can add the web reference to the desktop app. When I run the app in the same machine that is hosting the WCF service, it works fine, so I installed the system in one client for beta testing. When the client run in the server all requests made to the web services works fine, but this client has 2 remote stations, which have to consume as well the WCF service, now this is the issue, some times the request is not arriving to the WCF, I already added exceptions to the antivirus and firewall, so there is nothing blocking the communication between the server and the client stations.
I'm wondering if all the problem is because an incompatibility issue between the asmx extension and WCF service, but I don't find any after hours googling.
I appreciate any advice about this, the client is a beta, but is pressing hard to get a solucion ASAP.
I know this is going to sound stupid - but we've spent close to 4 weeks trying to implement a WCF callback system (Subscription Service), but to no avail.
Can anyone verify that they have successfully got this working in a multiple client production environment?
All the examples I've come across work on localhost but in production fails miserably.
The specific problem is that subscriptions and un-subscriptions work perfectly, up until the client is closed and re-opened at which point; multiple CallBacks are made or the Publish Method times out.
Again, can anyone confirm they have this working, or perhaps direct me to some documentation that provides a real-world PROVEN example.
Background info on my existing configuration found here:
WCF to WCF Communication
Thanks
I have WCF service project.Everything worked fine on Development Server.But I wanted to use net.tcp binding and for this I have set IIS 7.0 server in properties of WCF project.
I got a trouble, Error HTTP 404.20 - Not Found (No default document).Clinet is ASP.NET MVC 3.
Please help
Doesn't work that way. When published in IIS, a WCF service with an endpoint over net.tcp needs to have a net.tcp site binding.
Then, the Windows Activation Service (WAS) comes into play.
It's actually a pretty long story.
I suggest you first publish your service in IIS according to these instructions: http://galratner.com/blogs/net/archive/2010/10/08/setting-up-a-nettcpbinding-enabled-wcf-service-in-iis-7.aspx
If it still doesn't work, then post back with extra info.
Note: Extra reading, extra-extra reading.