Opening DLLs
in [VbScript]
|
From: Mike B on 11 Jan 2010 12:40 "mayayana" <mayaXXyana(a)rcXXn.com> wrote in message news:etxkdjtkKHA.1536(a)TK2MSFTNGP06.phx.gbl... > This post is so full of misleading untruths that > it smells to me like a post planted by Microsoft. > (And that's not a paranoid statement. MS is > famously documented to do such things. > http://www.groklaw.net/articlebasic.php?story=20071023002351958 > > > What you're saying is that it's foolish to look for > a scriptable solution when the OP could learn a new > programming language and write a DLL with a slow, > bloated 300 MB dependency that may not be installed > on the target machine. > <applause> synopsis accepted. </applause>
From: mr_unreliable on 11 Jan 2010 14:24
p byers wrote: > Thank you for your advice - it was very comprehensive. > You are welcome. > You said "(other than my own API Toolkit)" - please tell me a URL > so that I can have a look at it as well. > Sorry, I should not have mentioned the "API Toolkit", it is no longer in the public domain. However, for completeness sake, I should mention yet another actX object that may be used to call system api's from script. It is named "DynamicCall", written by Paul Guerra, and found on the Planet Source Code website: http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=55777&lngWId=1 I regard "DunamicCall" as an excellent piece of work. The (vb) source is provided and the coding is very competent. In addition, the set of parameter types acceptable to DynamicCall is "more robust" (a.k.a. more complete) then DynaWrap/DynaCall. Even more importantly, DynamicCall handles both [in] and [out] parameters, something either difficult or impossible to do with DynaWrap/DynaCall (depending on your skill level). It also comes with a number of test cases. Unfortunately (for me) it is one of those "good-news/bad-news" situations. The good-news you already know -- it looks like a good piece of work. The bad news (for me) is that Paul did not include the binary with his download. The code is "very" vb6-ish, in that my vb5(cce) can't handle it. I am ok with back-fitting the InStrRev and Split functions, but vb6 extended what you could do with UDT's (user defined types). I am still trying to figure out a way to re-write Paul's UDT's in such a way so that vb5 will compile them, and so that I don't have to extensively re-write Paul's code. In other words, even though I am recommending it, I haven't been able to actually _use_ DynamicCall yet. If there is any public-spirited vbs-er out there with a vb6 compiler installed and some spare time on his/her hands, it would be of great public service (to those scripters who are agreeable to the notion that using the system api from script is acceptable behavior) -- to post a copy here of the _compiled_ DynamicCall.dll. cheers, jw |