Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual basic CodedUI search for window name
    primarykey
    data
    text
    <p>I have a recorded item that can changes its window name dynamically depending on the runs. So using "Contains" to find the window name is a good idea, but implementing it does not seem intuitive.</p> <p>I successfully changed this:</p> <pre><code>'Me.SearchProperties(UITestControl.PropertyNames.Name) = "ex(3)" searchLimitContainer.SearchProperties.Add(UITestControl.PropertyNames.Name, "ex", PropertyExpressionOperator.Contains) </code></pre> <p>But cannot find how to replace this:</p> <pre><code>Me.WindowTitles.Add("Microsoft Excel - ex[3].xls") searchLimitContainer.SearchProperties.Add(UITestControl.WindowTitles.Add, "Microsoft Excel -", PropertyExpressionOperator.Contains) //Does not work UITestControl.WindowsTitles.Add or WindowsTitles.add does not exist </code></pre> <p>Where can I find the proper call(not only for this one, but all the ones I would need)?</p> <p>P.S. Yes I looked at the documentation, I did not find what I wanted.</p> <p>Similar problems: <br /> <a href="https://stackoverflow.com/questions/8816671/codedui-how-to-go-about-for-search-property-of-window-when-its-title-name-keeps">CodedUi :How to go about for search property of window when its title name keeps changing?</a> <br /> <a href="http://blogs.msdn.com/b/anutthara/archive/2009/08/19/using-regular-expressions-to-locate-controls-in-coded-ui-test.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/b/anutthara/archive/2009/08/19/using-regular-expressions-to-locate-controls-in-coded-ui-test.aspx</a> <br /> <a href="https://stackoverflow.com/questions/4140523/vs-2010-coded-ui-test-not-finding-window">VS 2010 Coded UI Test Not Finding Window</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload