Hi Rick,
How about product ID, or Process ID, each should have a unique number
associated with it running.
Bruce
Sent: Friday, May 04, 2012 8:05 AM
Subject: Stopping An External Script
Hi:
I am creating a script in VB.net 2008 for VB.net 2010.
I check the ProductName and attempt to close the script if it is not vb.net
2010 which opened it.
The Application.Exit() fires ok but the script is not stopped.
So:
I open vb.net 2008 to do some editing on the vbnet2010script, the ModuleName
is something like VBNetExpress which is the same as it is in vb.net 2010.
WindowEyes sees the VBNet module name and starts the vb.net 2010 script:
In the vb.net 2010 script I check for the ProductName containing 2010:
Since it contains 2008 I execute Application.Exit()
I go into WE ScriptManager and the vb.net 2010 Script is not stopped.
How do I stop the script without closing the vb.net 2008 IDE?
Is there some way of preventing WE from opening it in the first place?
What about killing the script process?
If not sure I will experiment but if there is a means of doing this like the
StopScript command in the script object that would be cleaner and more
efficient, especially if done before the script loads.
Rick USA
