I have created a sample Grpc application with a basic ado .net query and I want to host the same in the IIS. The application works fine when I consume it from a net client but after hosting, I am getting an error in the client application when I try to consume the grpc endpoint.
'Status(StatusCode="Unimplemented", Detail="Bad gRPC response. HTTP status code: 404")'
I have created an entity a grpc app with ef core and a WCF service with EF6. when I compare the response times, the WCF service seems to respond quicker than grpc app. Am I missing anything?
Related
I have a .NET Framework application which cannot be ported to net core for various reasons. Now I want to switch from Grpc.Core to Grpc.Net.Client because the first one gets deprecated.
May application makes a gRPC request to a service written in C++ which does only support HTTP/2 and does not provide TLS. According to here this connection is not supported: "Only gRPC calls over TLS are supported.". I can confirm this so far.
Is there any way to call a gRPC HTTP/2 service from a .NET Framework application without using TLS?
You could make a proxy service in which you call original gRPC with TLS.
Than from your application call this proxy service which doesn't have those restrictions.
Your app <--> proxy service <--> gRPC
Proxy service - implemented in one language you like and exposed to your application.
This is one posibility.
I have a site published in a IIS Server, but now i am adding a Connected Service using a WCF Soap to access another server.
Basically, my site needs consult a information from another server, and to this he needs to WCF.
When i publish my site in my homolog server, he death, and returne HTTP ERROR 500. However, in a localhost is normal.
I'm using a netcore 2.2
I have recently hosted my .NET Core WebSocket server on Azure but I can't communicate with it from any client at all.
I used to host it locally on "wss://127.0.0.1:8080" using a self signed ssl certificate and everything worked fine, I also hosted it using SAP Hana Cockpit (uses Cloud Foundry api) and it worked if started on "http://0.0.0.0:8080", and I accessed both via "wss://ADDRESSWITHOUTPORT" from my angular client and both work fine.
When I host it on Azure and try to use it from client, it gives me Unexpected Response Message 200 (WebSockets don't even have that error, iirc), changing port/address/protocol doesn't seem to do anything at all.
What should I do?
If it's useful, this is my project https://github.com/JamesMaloney/WebSocketServer.NET
Thanks in advance, Giacomo
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 have a WCF Service built with .NET Framework 3.5. I have a task to develop a WCF Client which only uses .NET Framework 2.0. The WCF Client will receive messages which is broadcasted from WCF Service. Can I do this?
The WCF Client runs well on a computer has .NET Framework 3.5. However on a computer which only has .NET Framework 2.0, and including WCF's DLLs in application's folder, WCF Client only send message to service ok but can't receive message from WCF Service.
WCF Client ---> WCF Service : OK
WCF Client <--- WCF Service : Not OK
Please help me. Thanks.
If your service exposes a basicHttpBinding endpoint, then you should be able to consume it in a .NET 2.0 application by using "Add Web Reference".