Quote:
Originally Posted by noobie
just use Socket#Connect instead of Socket#BeginConnect.
|
Not an option. I don't want my program blocked while the tcp/ip stack is doing stuff, like resolving, or connecting. That's just annoying.
The article is definitely interesting, but it applies to .NET 1.1, and I'm working with 2.0, and these methods are new to 2.0.
At any rate, thanks for yer help. I'll get it figured out. At worst, it's annoying, at best, it doesn't happen.
Not pouring much more time into it, right now. I can get it to connect, want to start getting the real meat of my app coded and functioning.
