Yeah, sometimes classes are in unexpected folders.
Socket isn't under System.Net, but just System, for some reason.
https://github.com/mono/mono/blob/master/mcs/class/System/System.Net.Sockets/Socket.cs
Marcelo Zabani wrote
Hi all, I've found something strange with the Socket.IsBound property.
On 12.11.2013 11:29, Stifu wrote:
Yeah, sometimes classes are in unexpected folders.
Socket isn't under System.Net, but just System, for some reason.
The reason is that Socket is implemented in the System assembly.
$(Assembly)/$(Namespace)/$(Class).cs
=
System/System.Net.Sockets/Socket.cs
Hi all, I've found something strange with the Socket.IsBound property. It
returns false on a connected TCP socket, while in Microsoft .NET it returns
true. According to the docs, it seems that it should indeed return true.
Is this a known issue (I didn't find anything in the bug DB) or should I
