Results 1 to 7 of 7

Thread: Winsock vb 6 vs vb 2008

  1. #1

    Thread Starter
    Junior Member
    Join Date
    Dec 2009
    Posts
    23

    Winsock vb 6 vs vb 2008

    hmm i have winsock for vb 2008 and for vb 6

    but in 2008 not all commands working like
    Winsock1.Accept RequestID
    or more you dont know why ?

    u know i like more working in vb 2008 this is why im asking if im no have old winsock ? for vb 2008 i have there kollman koding
    and normal microsoft corporation COM

  2. #2
    Hyperactive Member Philly0494's Avatar
    Join Date
    Apr 2008
    Posts
    485

    Re: Winsock vb 6 vs vb 2008

    Winsock works just fine in VB.NET, I use it all the time.

  3. #3
    Lively Member
    Join Date
    Dec 2009
    Posts
    86

    Re: Winsock vb 6 vs vb 2008

    Quote Originally Posted by Philly0494 View Post
    Winsock works just fine in VB.NET, I use it all the time.
    could you please pass a sample? I sort of got the same problem

  4. #4
    Hyperactive Member Philly0494's Avatar
    Join Date
    Apr 2008
    Posts
    485

    Re: Winsock vb 6 vs vb 2008

    where are you guys running into trouble?

  5. #5
    Lively Member
    Join Date
    Dec 2009
    Posts
    86

    Re: Winsock vb 6 vs vb 2008

    Quote Originally Posted by Philly0494 View Post
    where are you guys running into trouble?
    I dont want to hijack his thread so made my own.

    http://www.vbforums.com/showthread.php?t=597962

  6. #6

    Thread Starter
    Junior Member
    Join Date
    Dec 2009
    Posts
    23

    Re: Winsock vb 6 vs vb 2008

    Quote Originally Posted by Blixa View Post
    I dont want to hijack his thread so made my own.

    http://www.vbforums.com/showthread.php?t=597962
    its ok you can write here its better then it will be maybe faster solved why the winsocks on vb 6 have other codes like in vb 2008 :/

  7. #7
    Lively Member
    Join Date
    Dec 2009
    Posts
    86

    Re: Winsock vb 6 vs vb 2008

    Basicly my connectionRequest event is never launched however the client triggers the 'connectEvent'. I assume its that there is something wrong with the connectionRequest.

    Code:
    Private Sub sock_ConnectionRequest(ByVal sender As Object, ByVal e As AxMSWinsockLib.DMSWinsockControlEvents_ConnectionRequestEvent) Handles sock.ConnectionRequest
            writeLog("accepting new request id" + e.requestID)
            If sock.CtlState <> MSWinsockLib.StateConstants.sckConnected Then
                sock.Close()
            End If
            sock.Accept(e.requestID)
    End Sub

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width