Click to See Complete Forum and Search --> : How do I create an ActiveX like control in Vb.net?


cgchris99
September 10th, 2002, 02:28 PM
I am fairly new to vb.net.

I have the source code to a vb6 ocx that I want to re-create in vb.net. I think I can make it faster because of the new networkstreams.

How do I create a new control or activeX in vb.net?

This control is not for web based app so asp will not help me I don't think

Thanks for any advice

DSJ
September 10th, 2002, 04:05 PM
File... New... Project... in the "Templates" List, choose Window Control Library... (This will be a .NET user control NOT an ActiveX Control... those are goners...)

Platinum Plus
September 19th, 2002, 03:45 AM
(This will be a .NET user control NOT an ActiveX Control... those are goners...)



But just a few days ago MS was hailing ActiveX as the thing :cool:

WillemM
October 5th, 2002, 01:46 AM
LOL

yeah that's right. But ActiveX and win32 dll files are as good as history now. ActiveX was part of the dll **** in windows. And ms said they would solve that problem with the coming of .NET technologies.

As far as I know now the .NET framework delivers you the solution to the dll ****. One-time dll file installation and never again ! Since all apps are based on the same files, nothing can create conflicts. These dll files are not alterable so messing up the framework isn't possible.
I think .NET is the best product ms ever made. Ok ok I agree that it still has a huge amount of errors but that's about to be solved !

makai
October 8th, 2002, 01:13 AM
Totally confusing response - More questions than answers:

>As far as I know now the .NET framework delivers you the solution to the dll ****.

what is or was a four star DLL (I have eliminated an hotel rating)


>One-time dll file installation and never again
so is that supposed to be new?

>Since all apps are based on the same files, nothing can create conflicts.

all apps based on the same files - do you mean you can call a .NET DLL from any language?

Sure can't figure how that premise leads to no conflicts - isn't there more room for conflict somewhere?


>These dll files are not alterable so messing up the framework isn't possible.

You mean you can not change a DLL? seems obvious that you can - so what are you talking about here?