susall Posted December 11, 2008 Share Posted December 11, 2008 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.aspxTo 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 Link to comment Share on other sites More sharing options...
zfisherdrums Posted December 14, 2008 Share Posted December 14, 2008 (edited) susall, Follow the link in my signature ("Identify .NET controls by their design time names"). Zach Fisher... Edited December 14, 2008 by zfisherdrums Identify .NET controls by their design time namesLazyReader© could have read all this for you. Unit Testing for AutoItFolder WatcherWord Doc ComparisonThis here blog... Link to comment Share on other sites More sharing options...
susall Posted December 15, 2008 Author Share Posted December 15, 2008 susall,Follow the link in my signature ("Identify .NET controls by their design time names").Zach Fisher...Bless you, my friend! Bless you!-su Link to comment Share on other sites More sharing options...
susall Posted December 15, 2008 Author Share Posted December 15, 2008 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 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now