Jump to content
junkew

Advanced: COM versus RAW dll call

Recommended Posts

junkew

I was reading today a little in the reference sources of Microsoft on the UIAutomation stuff from .NET

In that (https://referencesource.microsoft.com/#UIAutomationClient/MS/Internal/Automation/UiaCoreAPI.cs,fd71c397cd77ad1c) I found for example this 

[DllImport(DllImport.UIAutomationCore, EntryPoint = "UiaGetRootNode", CharSet = CharSet.Unicode)]
        private static extern int RawUiaGetRootNode(out SafeNodeHandle hnode);

And based on that found this interesting article

https://blogs.msdn.microsoft.com/winuiautomation/2010/11/03/porting-our-provider-to-the-uia-com-api/

That raises to me the question

1. can I use native entrypoints in dll as opposed to the com/objcreateinterface solution?

2. Would it be easier then what I did so far in UIAutomation UDF in examples section?

edit: https://msdn.microsoft.com/en-us/library/windows/desktop/ee671214(v=vs.85).aspx

So seems to be documented however deprecated in favor of the com interfaces (which seems to be a wrapper around the deprecated functions ;-) ) 

Edited by junkew
seems deprecated funcitons

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.