Reputation: 4112
I am currently evaluating a requirement for a project for which I am considering SignalR. Here is a brief:
We want to have a server at our end that can send instructions to a client piece sitting somewhere in the world. The client piece then is supposed to do some local processing and send back a response that the server will show to the user. The client piece by itself should also be executable and generate the report. So we need some .net Code(console) at the client end(across the world) and some code at the hub end(our end). Although this is not a ASP.net application I feel like this is a good fit for websocket communication. I am looking for some guidance on getting a very very basic structure chalked out as I am new to SignalR.
Technologies : .net 4.5
Upvotes: 0
Views: 3125
Reputation: 1439
Follow the guides for setting up your hub and using the .Net Client. Essentially, the console applications are clients to your hub. Think of the hub as a relay. You can google "signalr console application" and get plenty of information on how to set that up.
Upvotes: 1