Re: TCP Streams from Unknown source to VB.Net

Hi, KnockNrod:

You can use usocket.dll inside our SocketPro at www.udaparts.com to
communicate with any types of other platforms on TCP/IP communication. You
can see the old VB6 sample at ..\SocketPro\samples\others\client\vb6\gethtml
after downloading and install.

Note that the usocket.dll is completely free and supports SSL/TLS to
secure socket communication as shown in the above sample.

Furthermore, we have CE versions of usocket.dll inside the directory
...\SocketPro\binCE\ARMV4 and ..\SocketPro\binCE\emulator.

Wish the usocket.dll is a big help to you.

Regards,


"knockNrod" <knockNrod@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A15721F7-68ED-4D0B-B609-C6A29DEBFBF7@xxxxxxxxxxxxxxxx
I'm trying to figure out how all of this is supposed to fit together.
I've
got a C/C++ application on a server, could be Unix, OpenVMS, or Windows -
definitely unmanaged, in every sense of the term - and it's sending
real-time
data back to a desktop with a Visual BASIC .Net interface. On the server
or
remote computer, a data structure is created, a header attached to tell
the
client what type of message and how many bytes, and the entire contents of
the data structure is sent in binary format out over a socket.

How do I receive that in Visual Basic .Net? Structures in VB.Net, aren't
structures, they're objects, and for some reason these structure objects
can't contain arrays. (Although arrays in VB.Net aren't arrays, either --
they, too are objects, so to be technically correct, I should say that the
Structure Object isn't allowed to contain an Array Object in VB.Net.)

I thought it was MS intent or vision to use a binary formatter object to
suck in this data through a structure object by making the structure on
the
VB side serializable and then it would all line up nice and neat like it
used
to in VB6. What I'm reading on here is that .Net remoting, that is, using
the binary formatter object, still won't understand the messages coming in
from the server. Is this possible in .Net? Should I plan on abandoning
.Net
altogether and replatform the interface in unmanaged (MFC/API) code?
(Yuck!)
I've got to admit that I'd rather switch to another operating system if it
came to that.

I have some control over the server source code, but I can't just migrate
it
entirely into .Net because some of our customers insist we still support
their existing systems which can be Windows, (L)Unix, and VAX/VMS. As far
as
I know, .Net framework only exists on Windows boxes, so the more I move
the
server into the .Net realm, the more complicated and expensive the server
code is to maintain. I'd rather tame the VB.Net code, if that's possible.

Any thoughts or suggestions would be appreciated! I'm really pulling my
hair out on this.

-rod


.

Relevant Pages

  • Another question about OpenOffice (and component based programming in general)
    ... if my program is going to connect the OO server via socket 8100 ... there is some sort of communication going on. ... If pipe: what is the name of the pipe? ...
    (comp.lang.java.programmer)
  • Re: stop Socket.BeginReceive before comlpete
    ... Peer-to-Peer Communication Across Network Address Translators ... you will also need the socket to listen to the ... coordinate the two clients). ... Can you enlaborator how did you listen to the Server? ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: creating server socket program to handle multiple client at same time
    ... > if no then select is only thing to have server socket program on one ... > pc and other clients on many pcs to have communication with server? ... accept returns a socket file descriptor ... forking a child you can have a select call and pass this descriptor to ...
    (comp.unix.programmer)
  • Re: Winsock & IO Completion problem
    ... And it's not a problem to have server and client on both ... I am implementing a communication framework, ... 5.Associate the socket B with the thread pool. ...
    (microsoft.public.win32.programmer.networks)
  • Re: How to terminate a socket in CLOSE_WAIT state
    ... FTP Server fixed for certain FTP clients who use both passive ... This was causing a PASSIVE opened socket to be left ... but instead expect the "half close" from the receiver. ... this sends a TCP/IP FIN packet to the ...
    (microsoft.public.win32.programmer.kernel)