I\'m reading the documentation on TcpClient.Close() and noticed this:
Calling this method will eventually result in the close of the associated Socket and
NetworkStream and TcpClient implement IDisposable. So best practise in my opinion is to pack it into a using block, so you never need to close or dispose it manually.
Closing the client does not close the stream, it's in the doc of the GetStream method. For the reference, have a look to this discussion : How to properly and completely close/reset a TcpClient connection?
Responding to this question since no one else did so that I may accept an answer.
According to Hans, calling NetworkStream.Close() is unnecessary because TcpClient.Close() closes its underlying NetworkStream.
You should Just do "TcpClient.Close()"
Or if you must, type both