Windows Automation API 3.0 has shipped!

  • Article

Greetings,

 

I am proud to announce that our Windows Automation API 3.0 Platform has shipped to Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008. Our platform now provides a consistent API surface for both providers and clients to create solutions for customers all supported Windows platforms. This release enables ISV’s to adopt the Windows 7 platform by allowing them to transition to UIA for both down-level and Windows 7 customers and accelerate the move by developers from MSAA to UIA.

 

 

What are the details of the package

We released 5 major packages. 32-bit versions for Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. We shipped 64-bit versions of Windows Server 2003, Windows Vista, and Windows Server 2008. In addition, we supported all major languages for each of the operating systems. If the language was a base language on the down-level platform and the resources were built for Windows 7, our package supports that language.

 

How will customers install the new software?

The packages will make their way down-level in these scenarios:

·       Many users will install these updates by default. The Windows Automation API will be installed as a recommended update from Windows Update on the client and server SKU’s of XP and Vista. 

·       Customers can download the installation packages from Microsoft Download Center. 

o https://support.microsoft.com/kb/971513/

·       In the next major service packs for each down-level platform, the updates will be included. Any new media that is sent to customers with these service packs will already have our latest platform on them.

·       ISV’s can use Windows Update API’s to see if the package has not been installed during their own software installation. If it has not been installed, they can use Windows Update API’s to automatically pull the package to the user’s machine and install it.

 

If you have any other questions, please us know! 

 

Sincerely,

 

The Windows team

Comments

  • Anonymous
    November 20, 2009
    Hey. Fantastic work! Does this include the COM client API for use with C++ in Windows XP? Been waiting anxiously for the IAccessibleEx interface :)

  • Anonymous
    May 12, 2010
    Yes, that exactly what it includes.

  • Anonymous
    June 04, 2010
    thanks good <a href="http://www.oyunagir.net">oyun oyna</a> Does this include the COM client API for use with C++ in Windows XP? Been waiting anxiously for the IAccessibleEx interface :)

  • Anonymous
    October 07, 2010
    Why not release a package of UIA for XPX64 operating system? If I want to use it in XPX64, what kinds of things have to do? Thanks!

  • Anonymous
    October 31, 2010
    What about win7? is Windows Automation API 3.0 installed by default? or should I install it manually? how can I tell (xp/win7) if Windows Automation API 3.0 is installed? 10x

  • Anonymous
    October 31, 2010
    What about win7? is Windows Automation API 3.0 installed by default? or should I install it manually? how can I tell (xp/win7) if Windows Automation API 3.0 is installed? 10x

  • Anonymous
    October 31, 2010
    What about win7? is Windows Automation API 3.0 installed by default? or should I install it manually? how can I tell (xp/win7) if Windows Automation API 3.0 is installed? 10x

  • Anonymous
    November 03, 2010
    Mighty. Create an COM client instance of some UIA interface, and check the HRESULT. You'll get E_NOINTERFACE if they are not installed.

  • Anonymous
    September 09, 2011
    Hey All,     The Definition of IUIAutomationElement.UIA_RuntimeIdPropertyId states that: "Identifies the RuntimeId property, which is an array of integers representing the identifier for an automation element. The identifier is unique on the desktop, but it is guaranteed to be unique only within the UI of the desktop on which it was generated. Identifiers can be reused over time. The format of RuntimeId can change. The returned identifier should be treated as an opaque value and used only for comparison; for example, to determine whether an automation element is in the cache." The part about "Identifiers can be reused over time." is unclear to me, can anybody explain what that means more clearly, specifically i want to know if this is unique per instance of the given application? Is this runtimeid reused in the same instance of the given application? Thanks in advance, Ray