Hi Kate: I heard some time ago that WPF was one of the Hhighest priorities of GW. But, that was the last I heard of that. I have mucked about vb.net 2010 with WE but found it pretty much useless compared to using vb.net 2008. I guess there are other screen reader choices available that work pretty well but I've not tried them since I think I can make WindowEyes do what I need it to do when I need it to do it with scripting. Also, I don't want to drop a grand on software that I use basically as a hobbiest, won't drop a grand for that purpose. The Express versions do what I need them to do. I would have dropped a couple hundred for the Standard version but that has been discontinued and it, like the express modules, couldn't natively handle add-ins from what I remember. So, I'll just use the Express modules and script them as necessary to work well. If anyone ever wanted Visual Studio scripped or add-ins created that would cost a bundle as the software alone is that expensive and I have no itch to do it for fun. Later and good hunting Kate! Rick USA ----- Original Message ----- From: Katherine Moss To: [email protected] Sent: Monday, December 12, 2011 8:40 AM Subject: RE: Visual Studio 2010
If you still have a copy of JAWS, it should work. I mean, if you're really serious about development, then you should look into the pro version anyway. VS 2010 has no standard version anymore. They took that one off. I just switch to JAWS when I want to use Vs 2010. But it would be nice for WE to have support for it, but I think that until GW Micro decided to make strides to support WPF fully, that's not going to happen. From: RicksPlace [mailto:[email protected]] Sent: Monday, December 12, 2011 4:26 AM To: [email protected] Subject: Visual Studio 2010 Hi: Visual Studio Express does not expose the COM interface unless you buy the Professional Version. That means no add-ins for the Express nor the Standard Versions as far as I can tell. I ran Jamal's HarvestWindow app and it looks like the MSAA stuff is still there and, if GW has done it all, the UIA stuff should be exposed through their MSAA and other objects from what I understand. I don't know about scripting the WPF objects which are what is used in all the new Microsoft Software and in Visual Studio in particular. Has anyone used a WE Script to do some scripting of the Visual Studio environment and especially the Editors and Designers? What about the WPF stuff? What about interacting with the DOM controls which are actually WPF in nature if I understand what I've read about the new Visual Studio? I am trying to find out if vb.net and vwd 2010 can be scripted without using add-ins as is being done for the VS Professional level, really expensive, software. Well, that's it. Without add-ins it may be a real mess to try and script that battleship but it is what it is. Some day my old machine will have to be replaced and I will be forced into windows 7 or 8 and likely have to install and use the newer Microsoft development software so I am starting to look at what I may have to do to reduce my learning curve when that happens. Rick USA
