Exceptions in Connect() not bubbled to caller

Question

Exceptions in Connect() not bubbled to caller

Closed this issue 10 years ago · 1 comments

If the underlying TcpClient throws an exception (due to host not resolvable or host not responding, for example), WaitForMessage task continues and no error is passed back to the caller.

Answer 1 · 2014-05-04T08:38:28.000Z

Fixed in 1.0.1.

Now checking state of antecedent task in WaitForMessage and throwing appropriately. Also changed Console.WriteLine to Trace.WriteLine for exposing exceptions inside message loop.