Results 1 to 5 of 5

Thread: Activex And VB.NET

  1. #1

    Thread Starter
    New Member
    Join Date
    Oct 2001
    Location
    Syria
    Posts
    13

    Activex And VB.NET

    I am about to begin studying ActiveX in Visual Basic 6.0.
    But some people told me that ActiveX in VB.NET is completely different, so
    don't waste your time in studying ActiveX in Visual Basic 6.0.
    and wait for VB.NET.

    Is this true.
    Will I waste my time in studying ActiveX in Visual Basic 6.0.
    Does ActiveX in Visual Basic 6.0. differ completely from VB.NET
    Luai AL Rantisi
    Syria - damascus
    P.O.Box 13017
    Phone : +963 11 6330264
    e-mail : [email protected]
    www.geocities.com/luairantisi

  2. #2
    I'm about to be a PowerPoster! Joacim Andersson's Avatar
    Join Date
    Jan 1999
    Location
    Sweden
    Posts
    14,649
    ActiveX is based on COM and .Net is supposed to replace COM.
    I don't agree about it being a waste of time though. Because it will take many many years before COM is dead.
    VS6 will still be around after VS.Net is released, MS will continue to sell and support VS6 along with the new version.

  3. #3
    old fart Frans C's Avatar
    Join Date
    Oct 1999
    Location
    the Netherlands
    Posts
    2,926
    Many concepts about creating ActiveX components with VB6 will will apply to creating .NET components with VB.NET also. So i don't think it is a complete waste.

    However, if you plan to convert these ActiveX components to .NET components I would suggest to build them in .NET in the first place and don't waste time in VB6.

  4. #4
    Lively Member Radar's Avatar
    Join Date
    Apr 2001
    Posts
    70
    I dunno.....
    I just took one of my custom VB6 ActiveX controls (compiled OCX) and used it on a .NET Windows form. For those interested, I first registered the control with Regsvr32. Then on the .NET menu I went to "Tools/Customize ToolBox" and added my control from the list. .NET went through a bunch of horse s**t and then made a "wrapper" class for my control. I could then access the control's properties etc. by referring to it by the wrapper class name in code. Not sure if all VB controls will work ok this way or not. Hope this helps...........Go ahead and learn VB6 too
    Aww screw it. I didn't really want to fool with it anymore anyhow.

  5. #5
    Black Cat JoshT's Avatar
    Join Date
    Nov 2000
    Location
    WNY, USA
    Posts
    4,032
    That's very similar to how you would have to wrap COM objects to use them with Visual J++...

    I wonder how many of MS's VJ++ team went on to work on .Net...
    Josh
    Get these: Mozilla Opera OpenBSD
    I have books for sale: "MCSD in a Nutshell" and "VB Distributed Exam Cram" - PM me for details. Will also trade for a decent ATX Pentium 2 MB/CPU/RAM combo.

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