Last post Mar 15, 2016 04:44 PM by h3david
Mar 13, 2016 09:16 PM|h3david|LINK
I hope you someone can help me here because I have no idea on what going on.
I'm creating an iot app that is supposed to exchange data with a WebApi using SignalR. I have been doing it for a while in debug and had no problem releated to SignalR until I decided to create a proper release package. The app starts properly on my iot
device (RbPi) but once a send a request to my WebApi server it is not forwatded to the RbPi.
I tried to look if the firewall was blocking any traffic so I add a rule to open every TCP port and in vain: (may I did it wrong)
netsh advfirewall FIREWALL add rule name="Allow any In 2" dir=in localport=1-65535 protocol=TCP action=allow
I also tried to monitor net traffic using the ETW of Windows iot ...nothing.
I have now no idea on where to look now, hope you can help.
Mar 15, 2016 03:10 AM|Fei Han - MSFT|LINK
Firstly, you could use Network tool to check the request status.
Secondly, you could enable SignalR tracing, which could help us to find and fix SignalR issue.
Mar 15, 2016 04:44 PM|h3david|LINK
Actually my issue wasn't related to SignalR. I posted my solution here => https://social.msdn.microsoft.com/Forums/en-US/a0231ec0-1afc-4384-a4d5-004376f3ec2d/signalr-windows-iot-webapi-works-fine-in-debug-but-not-at-all-using-a-release-package?forum=WindowsIoT
Hope it helps,