Slashdot Mirror

← Back to Stories (view on slashdot.org)

Visual Basic and ActiveX?

Posted by Cliff on from the does-one-need-the-other dept.

Dylbert asks: "Putting aside my gripes about using Microsoft products in the workplace (or anywhere, for that matter), I was wondering if any Slashdot users have found ways to overcome the forced use of ActiveX when creating DLLs in Visual Basic. Because my work uses a few seperate programming languages to write code in, the use of ActiveX would mean we will have to convert all our existing code to the same ActiveX architecture which I believe is unnecessary. Any suggestions?"

1 of 33 comments (clear)

  1. ActiveX == COM by euphline · · Score: 2, Interesting

    I don't quite understand your problem here. When you build an ActiveX DLL in VB, you are creating a COM DLL that can be used by anything that supports COM. I've even called ActiveX DLLs created by VB from _PERL_!

    ActiveX DLLs created in VB look no different to programs than any other DLL created by any other language that creates COM-compatible DLLs.

    What _doesn't_ work?

    -jbn