CODEWITHSUNDEEP
c#disposetcpclientnetworkstream
Ryan Peschel
Ryan Peschel

Reputation: 11848

Does one need to close both NetworkStream and TcpClient, or just TcpClient?

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 will also close the associated NetworkStream that is used to send and receive data if one was created.

So, correct me if I'm wrong but this says that if one calls Close() on the TcpClient that the NetworkStream will also be closed.

So then why at the end of the code example are both Close() called?

networkStream.Close();
tcpClient.Close();

Would it be just as fine to only call tcpClient.Close();?

Upvotes: 18

Views: 12187

Answers (4)

Vivien Ruiz
Vivien Ruiz

Reputation: 626

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?

Upvotes: 2

NickD
NickD

Reputation: 2646

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.

Upvotes: 2

user975017
user975017

Reputation: 89

You should Just do "TcpClient.Close()"
Or if you must, type both

Upvotes: -5

Ryan Peschel
Ryan Peschel

Reputation: 11848

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.

Upvotes: 18

Related Questions