Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a C# based server and some VB6 clients trying to connect to. The problem is that it seems that the clients are just randomly “missing” messages. myWinSock.Protocol is never set anywhere, so whatever the default value is is what the client’s WinSock will be. If the default was UDP that would answer my question and explain the loss of packets.
Is the default protocol for VB6 WinWock UDP or TCP?
In VB6, properties of controls are set in the designer, and there’s no generated property-setting code that would back up the choice made on the property sheet.
So you can’t tell that by only looking at VB6 code that the IDE shows you.
What you can do is click the winsock control icon and see what properties appear in the grid.
If you want to analyze a bunch of files in this way, you can look at the raw contents of
*.frmfiles, in the beginning of which you will see what properties are set for controls in the designer grid.That said, the default protocol for winsock is TCP. But you can never know if the default setting was preserved.