Sign in to follow this  
Followers 0
susall

a resolution to persistent Control IDs in .NET apps

4 posts in this topic

I found a great article on the problem of persistent control IDs in .NET. I'm using AutoIT as a way to automate an application written in .NET. It works well, except for the problem that the Control ID changes with every new build.

The following article out on MSDN addressed this problem:

http://msdn.microsoft.com/en-us/library/ms996405.aspx

To use AutoIT with .NET, I need a way to search for controls based on the Name property and using the WM_GETCONTROLNAME with a SendMessage. Before I go off and do this work, I was wondering if anyone had already implemented this solution already?

-sulu

Share this post


Link to post
Share on other sites



susall,

Follow the link in my signature ("Identify .NET controls by their design time names").

Zach Fisher...

Bless you, my friend! Bless you!

-su

Share this post


Link to post
Share on other sites

Workin' on it.... It keeps being unable to find the process, hence, returning a 1 for the control handle, instead of the control handle.

-su

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
Sign in to follow this  
Followers 0