Windows Socket Programming

Networks

Collapse -

Nothing to do with VB

by Tony Hopkinson · 11 years ago In reply to Windows Socket Programmin ...

If you are doing .net then the power is in the .net component you choose to use. So that becomes framework dependant. WCF (Windows Communication Foundation) in .NET 3.5 will give you considerably more options.

Straight VB is a total non starter for this sort of application, it doesn't have threading, don't even try.

As for most powerful, well if you want it raw then C/C++ is what you want, but that will require a significant amount of ability. The question you should be asking is will the 'off the shelf' framework compoents do the job, before you start re-inventing that wheel.
Try it with components first, get all the doings around it going them if you need to go under hood, all you will be writing is your own socket components. Best way to prepare for that is to stick everything to do with socket comms in it's own module and then whether you use MS, yours or any other will be competely transparent to what you you want to communicate.

Collapse -

Clarification

by globaldefenses · 11 years ago In reply to Nothing to do with VB

Okay. I guess another way of stating my confusion is this: Why can't you use VB if you have well-written objects, which do the socket manipulation, to link to? It seems that you should be able to call a DLL like CHILKAT which does the work, no?

Networks

Question