.net - How do you write a consistent UI Automation for MS? MSAA & UI Automation don't seem to overlap -


Work on a common automation tool, consider moving the Win32 message hook up to NIT UI automation, although the UI automation The feature set does not include all of us in Win32 and still does not support all GUI on Windows.

One such example is Windows Live Messenger.

Windows Live Messenger 2009 is still using the old DirectUIHwnd to attract the GUI. This means that you can not use windows messages to send in control, because the controls do not have its own HWND. This new The new UI also appears to defeat the automation framework, though the documentation appears to be such that it may include in the document. To indicate which MSAA can communicate with the content on which it has been shown.

Is there some trick to get the old MSAA technology that is trying to replace UI automation rather than working with UI automation?

Unlike Windows Messenger, there are not many solutions in trying to automate the same Windows for windows, where each of these techniques is legitimate and will work.

You probably want to see once, first was released as part of Windows 7, But now available for XP and Vista. I believe that support has improved in order to interact with MSAA-enabled goals.

This new API is COM-based, instead of being managed; But there is a look at CodePlex, it takes COM Api and makes it friendly to keep the "shape" similar to the existing "managed" UIAutomation API.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -