Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 27287 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 9962 [details]
A file demonstrating the problem. Remove the commented call FixNull to make it work as intended on mono.
When creating a new Socket using new Socket(SocketInformation), the RemoteEndPoint property will be null, even if the socket is connected.
I believe this is because seed_endpoint is never set to anything when using the new Socket(SocketInformation) constructor. In the attached file, I've added a method "FixNull" that sets the seed_endpoint field of the socket object to new IPEndPoint(0, 0). If this method is called (remove the commented line), RemoteEndPoint no longer returns null.