Hi Steve: You are right. They both run under the same executable name.
I will use the technique you mentioned, it makes sense.
Thanks.
Rick USA
----- Original Message -----
From: "Stephen Clower" <[email protected]>
To: <[email protected]>
Sent: Thursday, May 03, 2012 10:37 AM
Subject: Re: What Does WE Use To Associate A External Script with a Program
Rick,
The script is associated by module name. Thus, the 2008 and 2010 version
of Visual Studio Express probably run with the same executable name. What
you can do once the script loads is to interrogate the process responsible
for launching it and, based on product version, description, etc. you can
decide whether to continue running the script or cancel it.
Steve
On 5/3/2012 9:58 AM, RicksPlace wrote:
Hi;
I build a script in vb.net 2008 express to make vb.net 2010 Express
accessible:
I open vb.net 2010 Express and the script works to a point but...
The script is also assigned to vb.net 2008 Express which causes problems.
So my script is Associated with both VB.net 2010 Express - correctly but
also Associated with VB.net 2008 Express - incorrectly.
Unloading it while VB.net 2008 Express is active will Unload it for
VB.net 2010 Express as well.
What or how does WE associate a Script With an Application?
Can I override it or do anything to associate the vb.net 2010 script
soley with the vb.net 2010 Application?
Note that I am not running the vb.net 2008 version while I try and run
the vb.net 2010 version so the executable in the 2008 version will not be
tied up nor will, should, there be a duplicate set of processes running
for both 2008 and 2010.
Rick USA
--
Stephen Clower
Product support specialist & App Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
