Hi,
I've read a lot about the use of system sockets in Vb.net instead of winsock
fine but how do i get a vb.net service running on a 2003 server to send a
message to a desktop vb6 exe that can only use winsock?
So the service needs to send a message to the PC via some port say 8000.
The service knows the IP address of the PC also. The system socket code sends
the message and the VB6 exe has connected to the server on port 8000 but gets
no message. Am I missing the point here?
is there something different about the raw data passed by system sockets
that winsock cannot interpret.
Has anyone managed to do this?
BTW rewriting the desktop VB6 exe is not an option as it is massive and very
complicated and not needed if the exe can receive the message on the
designated port.
Can anyone help or suggest some other method.
As a last resort i may get the service to talk to an VB6 activex dll to get
it to send the message but surely this is un-necessary...
Thanks
Martin
