Yes, that should work just fine. Alternatively, if the executable is one
you wrote and does the things a WE external script needs to do, you
could use Application.StartScript.
(The list of those things can be found here:
http://www.gwmicro.com/mediawiki/index.php/Internal_and_External_Scripts#Responsibilities_of_External_Scripts
)
On 5/13/2011 10:10 AM, RicksPlace wrote:
Hi Ron: I want to create a VBScript to call a VB.net executable.
So, would a statement like the one mentioned:
Set oShell =CreateObject("Wscript.Shell")
and then use the shell run or execute methodWork in a regular
global script running under WindowEyes?
Thanks:
Rick USA
----- Original Message -----
*From:* Ron Parker <mailto:[email protected]>
*To:* [email protected] <mailto:[email protected]>
*Sent:* Friday, May 13, 2011 8:07 AM
*Subject:* Re: SharedObject Question
On 5/13/2011 7:18 AM, RicksPlace wrote:
Here is one of the statements in HomerSharedObjects.
Set oShell =CreateObject("Wscript.Shell")
I understood this statement would not run in a WE App but it does
in a SharedObject running App.
That's not the same WScript object you would use in a Windows
Script Host script to do something like WScript.CreateObject. It's
a separate object with a very similar name, which can be
confusing. You can use that object (and any object you can create
with CreateObject) in any WE script.
Is there something in the standard WSH WScript object that you
need? It should be possible to do anything you would have done
with the standard WScript object using either the Application or
Script objects in Window-Eyes scripts. (n.b. External scripts
don't get a Script object; we assume that whatever environment an
external script is running in has provided that functionality for
you.)
