Certain TcpClient (and potentially other class) constructors perform I/O

[CIPop]

Performing I/O in a constructor is not supported by the UWP policies if that constructor is called on an UI thread.
We need to investigate if we need to change the implementation, obsolete the constructors or at least document this behavior.

[stephentoub]

We need to investigate if we need to change the implementation

What's the exact limitation? It's it a technical thing (i.e. an exception occurs) or a policy thing (i.e. it's frowned upon and apps that do it are disallowed). If the former, I'm wondering if, for example, on UWP the I/O could just be moved off of the current thread, e.g. instead of:

Connect(hostname, port);

doing the equivalent of:

Task.Run(() => Connect(hostname, port)).GetAwaiter().GetResult();

to initiate the I/O from a non-UI thread.

[DavidGoll]

@stephentoub It's policy (to prevent UI hangs).
This issue was opened to determine whether these constructors are causing perceivable hangs.

[DavidGoll]

Triage: This is not expected to have any perceived impact. If it proves to be an issue (e.g., throwing on the constructor, hanging the UI), we will revisit. Will handle via new issues opened for the specific constructor(s) as they are opened.