Hi Kate: I understand your plight. The learning curve for the VS IDE and
it's thousand or so windows and wizards and designers is quite a task. Add
to that learning a language as obtuse as CSharp and just building coherrent
logic structures, Event Driven Modular and OOP programming concepts and, oh
ya, throw into the mix the very complex and hard to debug COM design and
implementation requirements along with system message processing, threading
and all that jazz and just this targeted path is more than can be picked up
all at once in my opinion. That is without turning your hair gray and taking
an AntiDepressent or two frequently.
Oops, dont forget about learning how to use the WindowEyes Scripting
Technicals to create the bones of a COM script and all the WE objects,
properties and events and only reference documentation for the most part to
work from.
There are existing scripts created in VBS but that is a major diference from
say a VB.net or CSharp program running under the Managed DotNet environment.
If you want to get into this arena I recommend doing the following:
Get your version of Visual Studio or one of the Express versions up and
running:
Set it up as much as you can in a static mode for easier learning of the IDE
operations via the Tools>Options menu item I think it is:
Create some simple programs with and without a form and, or, generate your
own form utilizing the Load and some other events like FormClosing etc...
You may not want to use a form in a WindowEyes script but it is the best way
to break into using event processing.
Next You would want to understand how to attach and process events within a
class that is not a Form so you can understand the first level of a VB, or
C#, COM interface like WE uses.
Once you can create programs with and without forms, use events and event
handlers in one of the several fashons available, you will understand how to
create a module and class with events that is required as the first step in
a DotNet, or other environment,script other than VBS or JavaScript.
If you get this far you will want to use a simple Message Processing
technique to send messages to your program and ensure it works. At this
point you might consider looking at COM and how it works and after playing
with it for awhile you might be ready to handle WE Scripting from within a
DotNet environment if they have all the buggs worked out.
Rick USA
----- Original Message -----
From: "Katherine Moss" <[email protected]>
To: <[email protected]>
Sent: Monday, November 28, 2011 11:19 PM
Subject: RE: how to know what to reclass controls as when encountered
You see, guys, the issue is that I'm leaning everywhere, and C# is just the
tip of the iceburg.
-----Original Message-----
From: Chip Orange [mailto:[email protected]]
Sent: Monday, November 28, 2011 8:23 PM
To: [email protected]
Subject: RE: how to know what to reclass controls as when encountered
Katherine,
ok; I don't believe COM interoperability is that much to learn, and there
are plenty of examples and info, easily googled, and Rick has mentioned he's
done this, and would probably be willing to answer your questions. The com
part of scripting in .net would, in my guess, be the least of all the things
you''ll need to learn; and my experience has always been, just start doing
something, and you'll be surprise 6 months or a year later, how much you've
learned, how much you've accomplished in that last time period.
Personally, I'd appreciate someone trying out iron.com and giving us some
examples of using the .net framework from VBScript if you're leaning that
way. If you're interested in Python, I believe there are some apps written
using it (such as the audio toolkit written by Steve Clower).
I can't remember if anyone mentioned it, but there are articles in the GW
wiki at http://gwmicro.com/wiki which are also designed to cover various
scripting topics.
hth,
Chip
hth,
Chip
-----Original Message-----
From: Katherine Moss [mailto:[email protected]]
Sent: Monday, November 28, 2011 7:56 PM
To: [email protected]
Subject: RE: how to know what to reclass controls as when encountered
What I'm saying is that I'm trying to use a .net language.
-----Original Message-----
From: Chip Orange [mailto:[email protected]]
Sent: Monday, November 28, 2011 7:51 PM
To: [email protected]
Subject: RE: how to know what to reclass controls as when encountered
Hi again Katherine,
I'm not really clear what it is you want to do; but, if you want to use the
dot net framework, without the bother and overhead of using a dot net
language and it's com interface to window-eyes, you could check out a app
from Jamal Mazrui named IronCom demo. It allows you to use the dot net
framework from VBScript, or if not allows you to do so, then demos how you
go about it.
hth,
Chip
-----Original Message-----
From: Katherine Moss [mailto:[email protected]]
Sent: Monday, November 28, 2011 9:25 AM
To: [email protected]
Subject: RE: how to know what to reclass controls as when encountered
I'm not afraid of doing that since my goal is to dabble in all of the .net
framework I can reach before Microsoft kills it.
-----Original Message-----
From: RicksPlace [mailto:[email protected]]
Sent: Monday, November 28, 2011 3:31 AM
To: [email protected]
Subject: Re: how to know what to reclass controls as when encountered
Hi Kate: If you are going to try and use a DotNet language like CSharp or
VB.net or any language other than VBS or JScript COM should be something you
should at least be familiar with since you will be mucking about trying to
interface with WindowEyes COM objects.
I tried to get a VB.net app working and did to a small extent but had
message processing problems I couldn't resolve at that time.
So, long story short, you should understand COM and how a CSharp Program
would interface with the WE COM object so you can understand the required
hooks necessary in your application and how to use the browser to find info
on WE InterOp objects.
Rick USA
