Unlike other variants, ReceiveFromAsync(saea) and ReceiveMessageFrom(saea) does not throw when socket is not bound

[antonfirsov]

When the socket not bound, all sync and async variants of ReceiveFrom and ReceiveMessageFrom seem to throw InvalidOperationException.

SocketAsyncEventArg overloads fail with SocketError.InvalidArgument instead. Furthermore: ReceiveMessageFrom hits an assertion failure, and on Unix ReceiveFrom does not fail at all.

I'm not sure if it's by design, or is it a something we want to change this for consistency.

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

When the socket not bound, all sync and async variants of ReceiveFrom and ReceiveMessageFrom seem to throw InvalidOperationException, except the SocketAsyncEventArg overloads, which throw SocketException. ReceiveMessageFrom also has a failing assertion in this case.

We may want to change this for consistency.

Author:	antonfirsov
Assignees:	-
Labels:	area-System.Net.Sockets, untriaged
Milestone:	-

[geoffkizer]

We should fix the assert at the very least.

on Unix ReceiveFrom does not fail at all.

What does it do, just never complete?

I think we should just change the behavior here to throw InvalidOperationException for consistency. It's a usage error so changing the exception is not a big deal. And that would address the other weirdness here as well.

[antonfirsov]

What does it do, just never complete?

Exactly.

[ManickaP]

Triage: it makes more sense to throw in advance for protocols that require binding, we should fix for 6.0.

[karelz]

Triage: UDP corner case, fine to move to Future.