I have run into a strange issue when using XcoAppSpace v1.4. I am running a XCoordination worker on a remote PC under the full .NET framework and I am attempting to connect to this worker using my WinCE device.
I have added a button to the WinCE WinForm app that attempts to connect to the remote worker using TCP for the transport and JSON for the serializer. However, every time I try to connect using this button I receive a socket error (error #10060 - connection timeout) then a XcoCommunicationException which states that there was a communication error.
The strange thing is that I can successfully connect to the remote worker if I attempt the connection within a locally hosted worker (on the WinCE device) that is invoked via a connection from the remote PC. The only difference that I can see in these two scenarios is that the scenario that fails is running in the WinForms thread context and the scenario that succeeds is running the the WinCE hosted worker context.
Any help with this would be greatly appreciated!
Comments: ** Comment from web user: thomass **
I have added a button to the WinCE WinForm app that attempts to connect to the remote worker using TCP for the transport and JSON for the serializer. However, every time I try to connect using this button I receive a socket error (error #10060 - connection timeout) then a XcoCommunicationException which states that there was a communication error.
The strange thing is that I can successfully connect to the remote worker if I attempt the connection within a locally hosted worker (on the WinCE device) that is invoked via a connection from the remote PC. The only difference that I can see in these two scenarios is that the scenario that fails is running in the WinForms thread context and the scenario that succeeds is running the the WinCE hosted worker context.
Any help with this would be greatly appreciated!
Comments: ** Comment from web user: thomass **
Hi Keith,
I did some more tests to ensure that the TcpClient Socket is really bound to the specified IP address, which really seems to be the case - strange that it doesn't help. But I'm glad that you at least found a workaround. Let me know when you find out anything that could help resolve the issue.
