Have you figured out any way to get that pesky intellisense to work at all -- if I turn it on, whenever it gives me a context menu, the cursor goes away once I select the item and I have to alt-tab away and back to get the cursor again. This is a bug, but I was wondering what your experience has been. Even the object browser does not always give good results.
RicksPlace <[email protected]> wrote: > Hi Chip: The Object Model is exposed in the Professional version for sure as > a COM interface. I think Microsoft did not do this in the lower versions > because folks could add functionallity via add-ins that Microsoft wants to > sell via their Professional version. > That said, Doug's comments lately and a little fooling around with Jamal's > harvest app have shown me that at the very least the MSAA stuff is there, the > Forms Designer may be a much cleaner thing to work with in 2010 and the UIA > stuff is available via non WindowEyes interfaces somehow - likely using a > language like VBS or some third party programming language. > In any event VS 2010 should be able to be scripted without the use of > add-ins. Perhaps it would be a bigger job and may, or not, be as perfect of a > solution but I think it should work well enough for my needs. > There are other inherrant problems, not WindowEyes related directly, that > I've yet to think about. One of them being the fact that the IDE doesn't > offer that MDI TabbedDocument setting which was used to make windows closable > using the ctrl-f4 key and so they didn't step on each other. I'm not sure how > to set that up, perhaps in a script. > As it now stands I have to manually close windows or my vb.net editor doesn't > read and I want it to read whenever I open it without mucking about the IDE > manually closing other windows. > Some of those windows will close with ctrl-f4 but others wont and I have to > close them from within the windows menu, or at least change their float, dock > or other setting to get the vb editor to read correctly. > Again, this sounds scriptable if I can't find some built-in VB.net setting to > eliminate this problem. > The Forms Designer looked pretty clean compared to the 2008 Forms Designer in > the DOM but that was a first, quick look so don't hold me to that. > Anyway, thanks for the heads up. Some day I will be forced to move up to > something other than XP and VS 2008 which I really, really like from an > accessibility standpoint and for quick development. > I should guess that for those folks who can drop the cash a add-in package > and the Professional Version would be the way to go but for me I think I will > be able to make the Express versions do just about everything I can think of > related to developing Websites, Windows Programs and DataBase Operations so > long as I can get at the DOM effectively and it looks ok so far. > Well, thats all I have this morning from dark and cold Farmington Michigan: > Later Chip and good hunting. > Rick USA > > ----- Original Message ----- > From: Chip Orange > To: [email protected] > Sent: Monday, December 12, 2011 8:55 PM > Subject: RE: Visual Studio 2010 > > > Hi Rick, > > At the site below, you can read about all the current versions of visual > studio (it's a MS site); it looks like professional is still available for > purchase also. > > Even better though is a link to trial versions of all the various editions, > so you could download and test professional to see if it does expose it's > object model (just search for the word "trial" to take you to the downloads > page). > > http://www.microsoft.com/visualstudio/en-us/products/2010-editions > > Now that we've got the answer from Doug, you know that scripting it is > possible, and I do suspect the object model is available in professional. > > hth, > > Chip > > > > > ---------------------------------------------------------------------------- > 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 > > > ---------------------------------------------------- > Alternatives: > > ---------------------------------------------------- -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici [email protected]
