VB.net 2 - Socket - Why is it so difficult?

[MTEXX]

There are dozens of snippets and such on the net of how individuals have wrapped the Socket class; yet none work for all situations. My question is- why? The VB6 Winsock control worked beautifully. I've also had experience with the Qt toolkit. Their QSocket worked likewise beautifully. Why did MS break a good thing? I suppose that is a moot subject.

Be it threading issues, synchronous lag, the necessity to wrap functions in a thread, unfixable exceptions I still can't get a socket implementation to work for a decent set of use cases. I've spent sum porobably 60 hours on sockets in vb.net and I'm growing VERY TIRED of dealing with it.

Where is a robust VB6-style implementation of sockets for VB.net 2?????? that's what i want!!!

Thanks in advance,

-MTEXX

[radcaesar]

When compared to vb6, .NET is the robust thing to achieve things. I thought that its ur problem because u still stick on the older ones. Refer MSDN Specification for 2.0 sockets.

Just be strong in those assembly collections of 2.0 and u will be fine to carry forward. Sorry, if i have degrade you or any mislead words. Just leave those words.

Thanks.

There are dozens of snippets and such on the net of how individuals have wrapped the Socket class; yet none work for all situations. My question is- why? The VB6 Winsock control worked beautifully. I've also had experience with the Qt toolkit. Their QSocket worked likewise beautifully. Why did MS break a good thing? I suppose that is a moot subject.

Be it threading issues, synchronous lag, the necessity to wrap functions in a thread, unfixable exceptions I still can't get a socket implementation to work for a decent set of use cases. I've spent sum porobably 60 hours on sockets in vb.net and I'm growing VERY TIRED of dealing with it.

Where is a robust VB6-style implementation of sockets for VB.net 2?????? that's what i want!!!

Thanks in advance,

-MTEXX