I used the DLLs from the C# example for both my C# example and VB
example. You can just as easily build your own using the wineyes.tlb and
tlbimp (http://msdn.microsoft.com/en-us/library/tt0cf3sx%28VS.80%29.aspx).
Aaron
On 4/13/2012 1:14 PM, RicksPlace wrote:
Hi Again Aaron:
You wrote:
Scripting.dll1.0.0.0 and
Windoweyes.dll.
Those are for the C# example, and are, therefore, included in the
C# sample zip.
Aaron, I am confused.
Those 2 files were from the VB.net example.
Are you saying they are no longer necessary for a VB.net Application?
Or, are you telling me to use the versions in the C# example?
Or, do I just not need them at all for a vb.net app?
If I dont need them where do I point the reference to access the
Windoweyes Application related Events, methods and Properties for
the COM interface and Object Explorer?
How do I include the reference in the Imports Windoweyes
statement, it would be the Using Windoweyes statement in your c#
example.
Rick USA
----- Original Message -----
*From:* Aaron Smith <mailto:[email protected]>
*To:* [email protected] <mailto:[email protected]>
*Sent:* Friday, April 13, 2012 10:47 AM
*Subject:* Re: Windoweyes SDK
On 4/13/2012 10:30 AM, RicksPlace wrote:
Scripting.dll1.0.0.0 and
Windoweyes.dll.
Those are for the C# example, and are, therefore, included in the
C# sample zip.
Aaron
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
