Clarification: all SKUs of Visual Studio 2010 should expose UIA. Older
versions do not.
On 4/27/2012 8:11 AM, Ron Parker wrote:
UIA and the DOM are orthogonal concepts. All versions of Visual Studio
should expose their UI through UIA, whether they expose a DOM or not.
On 4/27/2012 5:13 AM, RicksPlace wrote:
Thanks Chip:
I am still not sure if UIA is going to help at all with the Visual
Studio Express versions since they dont expose their dom like the Pro
level of that product and above.
At least that is what Ive heard.
Also, the Express versions dont allow Plug-Ins, Add-Ins, so that
method of improving their accessibility is out.
I guess I will just try vb.net 2010 more in-depth. While not as good
as 2008 it is accessible, pretty much, using WE. I really dont know
how WE managed to make it as accessible as it is.
As for the immenant release of VS 11 ... Metro sounds like a real can
of worms just like the Microsoft Phone OS which is totally
inaccessible as far as I know.
Rick USA
----- Original Message -----
*From:* Chip Orange <mailto:lists3...@comcast.net>
*To:* gw-scripting@gwmicro.com <mailto:gw-scripting@gwmicro.com>
*Sent:* Thursday, April 26, 2012 6:22 PM
*Subject:* RE: WE And Microsoft Development Environments
Hi Rick,
If you don't want to make it into a working script (and I do
think it would see a lot of use while .net users wait for better
accessibility), then you could always publish the source code in
a wiki article, with any explanatory text you care to add; that
would allow others to pick things up and continue development.
Chip
------------------------------------------------------------------------
*From:* RicksPlace [mailto:ofbgm...@mi.rr.com]
*Sent:* Thursday, April 26, 2012 4:48 AM
*To:* gw-scripting@gwmicro.com
*Subject:* Re: WE And Microsoft Development Environments
Hi Kate and Chip: I had heard that also.
For the Pro and above you can use plug-ins and I guess there
is more of a DOM available.
I was hoping to be able to use the existing DOM and MSAA in
the Express versions to clean up some of the less user
friendly features.
I just am not going to drop hundreds of dollars just to
create scripts, if they can be created for WE, when I use
the Express versions.
I can work around the problems manually for the most part
but would prefer a clean IDE with things all working
properly if possible.
Well, I am waiting for the final release version of VS 11
to see how it handles the new features like that Metro stuff.
By the way, MS has deprecated support for Macros in VS 11
if not in 2010 since they said less than 1 percent of
their clients use that feature.
I wonder what percent of their clients use UIA and ARIA
accessibility hooks?
Anyway, it is what it is so I'll close this thread with a
big thank you to you folks.
I have a VB.net script working so if anyone ever wants it
as a base to build from let me know.
It is in vb.net 2008 express so will likely be out of
date sooner rather than later but at least I finally have
it working thanks to some clean base code from Aaron.
Thanks Aaron, if you are reading this and good work you
old guru.
Later:
Rick USA
