NamedPipeClientStream.ReadAsync() continuously reads after the first message arrives
How come
NamedPipeClientStream.ReadAsync
continuously reads 0 bytes after the first message arrives?
Basically is there a way to have it asynchronously wait until more data arrives after the first message?2 Replies
uhm im pretty sure if the result is 0 there are no more bytes, stream is finished (like, marked finished from the other side)
I don't believe I'm intentionally finishing the server stream, here is my code:
After the first message arrives it continuously reads null as the line
I was being dumb and called dispose in the finally block instead of the catch