[Mono-bugs] [Bug 58169][Wis] New - Non-blocking connect returns incorrect error code.

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by michi@zeroc.com.

http://bugzilla.ximian.com/show_bug.cgi?id=58169

--- shadow/58169	2004-05-06 22:45:51.000000000 -0400
+++ shadow/58169.tmp.21250	2004-05-06 22:45:51.000000000 -0400
@@ -0,0 +1,29 @@
+Bug#: 58169
+Product: Mono: Runtime
+Version: unspecified
+OS: 
+OS Details: Redhat 8
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: michi@zeroc.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Non-blocking connect returns incorrect error code.
+
+When calling System.Socket.Connect() on a non-blocking socket, the
+exception that is thrown has a native error code of WSAEINPROGRESS (10036).
+This is inconsistent with the behavior of the .NET 1.1 Framework under
+Windows, which returns a native error code of WSAEWOULDBLOCK (10035).
+
+Looking at winsock2.h, WSAEINPROGRESS is marked as deprecated in winsock2.
+I think the Mono run time should behave the same way as the .NET one.
+
+Cheers,
+
+Michi.