|
-
Dec 14th, 2005, 03:01 PM
#1
Thread Starter
Frenzied Member
Socket.EndConnect doesn't throw exception
I've used the asychonous Socket methods quite a bit, but never bothered with .BeginConnect / .EndConnect, opting instead to use .Connect.
So I figured I'd try it just for kicks. I set up the IP address and port, and do not have anything listening on the port, so I fully expect to get a winsock error with the message "No connection could be made because the target machine actively refused it".
I get the expected SocketException when I use the .Connect method, but don't get it when I use the asynchronous methods. There's no exception on .EndConnect, yet the Socket of course isn't connected.
Anyone know why that is? I've searched around, but can't find anything useful.
Thanks,
Mike
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|