Winsock Control vs System.Net

[Robert]

Is there a reason I shouldn't use the Winsock ActiveX
control and instead use the System.Net and
System.Net.Sockets?

Thanks

Robert

 

[Cor]

Hi Robert,

There is always one to think about with every ActiveX, managed code is also
to make deploy more easy.

Just a thought,

Cor

 

[Scott]

Well, I've worked with Winsock control a lot in VB6. I think the .NET
classes are a great improvement over the ActiveX control. They allow more
flexibility and a more Object Oriented approach since you can inherit from
the classes to extend them. Also, I remember there being a memory leak in
the ActiveX control that was never fixed...

Scott

 

[Herfried K. Wagner [MVP]]

Is there a reason I shouldn't use the Winsock ActiveX
control and instead use the System.Net and
System.Net.Sockets?

No.

 

[Cor]

Hi Herfried,

No.

On which question?

Cor

 

[Guest]

I can think of a reason. The Winsock Control in VB 6.0 has memory leak problems. If I find the URL on MSDN about this issue I will give it to you.

 

[Guest]

Sorry I didn't see that somebody already mentioned this
BTW- I have seen it leak memory

 

[Scott]

Here's one article on the memory leak...

http://support.microsoft.com/default.aspx?scid=kb;en-us;171843

I've seen it happen before as well. I wrote a client/server app in VB6 using
winsock controls and the server would consume more and more memory to the
point where I would have to shut it down and reboot the server on occasion
which is rather irritating...

Scott

 

[Herfried K. Wagner [MVP]]

Cor,

On which question?

In other words: There is (IMO) no reason to use the "old" ActiveX
control (except for saving time when upgrading a VB6 project).