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?"

2 of 33 comments (clear)

  1. Um, just 'uncheck' the dialog by CounterZer0 · · Score: 1, Insightful

    You are not forced to use ActiveX in VB. It's a DLL compile option. If that gives you trouble, I seriously recommend getting a book on VB (it will at least explain the IDE and it's various options)...

  2. sorry for the dumb counter-questions... by kitts · · Score: 2, Insightful

    If your point involves making sure you can glue several languages together, why not just use one of the other languages for the dll? Visual Basic itself is going to mean a performance hit over and above dll usage, and not using ActiveX limits your choice of references (including no ado) and pretty much eliminates the visual controls.

    In the meantime, using ActiveX actually opens up a bunch of options, because an ActiveX dll, once created, can be called from within VB, VC++, ASP...

    --
    -------------------------------------------------- ----
    charlton heston is more of a man than yo