These are usually called "standard DLLs" as opposed to "ActiveX DLLs." There is nothing "industry standard" about them. It's an old, old technology - though it sure has its points! I'm not saying PB can't be compiled to an ActiveX DLL though, mainly 'cause I don't know much about the product.
However I do know that VBScript (or JScript, etc.) cannot call entrypoints in standard DLLs. This is a pain for lots of reasons, for example I'd love to be able to make calls to Windows APIs from VBScript.
Microsoft has no incentive to change this either. The Active Scripting tools are considered obsolete and "on the way out" (though we'll see, we'll see). They don't fit well into the ".Net scheme of things." But even a few years back it was unlikely to ever happen. Just look at all the flack they take because script can call ActiveX libraries!
I'm not surprised. I've lost count the number of times that I have moved from one stepping stone to another to get at something I couldn't do on the 'old' stone only to find that the 'new' stone will not do some things that I took for granted on the 'old' stone.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.