Equivalent usages section in TCP

[liveans]

Summary

Adding an article to show TcpClient usages equivalent to Socket under Use TcpClient and TcpListener.

Fixes one task from #31702

Preview

https://review.learn.microsoft.com/en-us/dotnet/fundamentals/networking/sockets/tcp-classes?branch=pr-en-us-32106

[liveans]

Creating new article is harder than I expected, can you do a quick review on it @IEvangelist @antonfirsov?

[IEvangelist]

A few nits.

[antonfirsov]

@IEvangelist are you aware about extensive docs on xref?

[IEvangelist]

@IEvangelist are you aware about extensive docs on xref?

Hi @antonfirsov - I'm not sure I follow your question here, are you asking if we have docs on how to write an xref? If so we have internal content on this here: https://review.learn.microsoft.com/en-us/help/platform/links-how-to?branch=main#xref-cross-reference-links

[antonfirsov]

@IEvangelist those docs are exactly what we need, thank you!

[IEvangelist]

@IEvangelist those docs are exactly what we need, thank you!

Yeah, the best way to use them is to rely on the Learn Authoring Pack extension in VS Code.

[liveans]

@antonfirsov Should we add more sections? Thoughts?

[antonfirsov]

We should try to be less verbose. This addition is intended to be a tutorial and general explanation, we don't have to explain all the details IMO.

[antonfirsov]

We should figure out how to create / fix the API links before merging.

[gewarren]

We should figure out how to create / fix the API links before merging.

This extension for VS Code makes it easy to insert xref (API) links: https://marketplace.visualstudio.com/items?itemName=docsmsft.docs-markdown

F1 -> Learn: Link to xref -> [type in some part of the API you want to insert]

[antonfirsov]

I have no more fundamental concerns about the structure/style.

@gewarren or @IEvangelist can you please take a look at the grammar/language here. There's a lot of text, and I'm not native.

[IEvangelist]

I have several nits, a few grammatical suggestions, some code adjustments, and a question or two. Otherwise, it looks good. I was also going to ask, why are there no using statements? I would like to see anywhere that we're showing IDisposable implementations that we're either showing them in a using, does that make sense? For example, instead of:

var client = new TcpClient();
NetworkStream stream = client.GetStream();

We'd show:

using var client = new TcpClient();
using NetworkStream stream = client.GetStream();

[IEvangelist]

I have no more fundamental concerns about the structure/style.

@gewarren or @IEvangelist can you please take a look at the grammar/language here. There's a lot of text, and I'm not native.

Hi @antonfirsov and @liveans - I have provided a review.

[liveans]

Hi @antonfirsov and @liveans - I have provided a review.

Thanks for the review @IEvangelist !

I would like to see anywhere that we're showing IDisposable implementations that we're either showing them in a using, does that make sense?

Well, it doesn't have a specific reason, tbh. I was focusing on equivalent code blocks, instead of those, but it makes sense to me. I'll address them with the next commit.

[liveans]

Merging this, I can make another PR for any follow up comment. @antonfirsov @IEvangelist