Printable View
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
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.
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.
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 :)
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...