Hay, thanks Ron. I think you are right. The modules that would be in the GWTool
Kit were for the Dictionary and strings and xml which I have removed. I just
want an extremely simple script that hooks up to WE, is associated with VWD and
just displays a MessageBox on entry and on ShutDown when I
On 6/21/2010 5:46 PM, RicksPlace wrote:
Am I correct that you Added Them as References using the Add Dialog in
VB.net by navigating to the dlls in the vbnet-example solution rather
than loading the Windoweyes Dll from the one in the COM Tab?
I think that's right, yes. It's been a while since I
s but I won't know until I try out the
alternative.
Rick USA
- Original Message -
From: Chip Orange
To: gw-scripting@gwmicro.com
Sent: Monday, June 21, 2010 8:15 PM
Subject: RE: WE DLLs And Developing a VB.net External Script
Rick,
while I can't answer your q
xternal_Scrip
ts
Chip
_
From: RicksPlace [mailto:ofbgm...@mi.rr.com]
Sent: Monday, June 21, 2010 5:47 PM
To: gw-scripting@gwmicro.com
Subject: WE DLLs And Developing a VB.net External Script
Hi:I am developing a Vb.net External Script based on the vbnet-example.
I have 2 question
Hi:I am developing a Vb.net External Script based on the vbnet-example.
I have 2 questions about the DLLs supplied with the Solution and one about the
WindowEyes SDK which the docs say is required for development.
Question 1:
In vbnet-example under the References folder are references to windoweye
