ContributionsMost RecentMost LikesSolutionsRe: AutomatedQA.TestComplete.CustomControls.dll could not be found with TestComplete 9.31 installWe actually found the assembly in the GAC and were able to extract it from there so that we could continue development of our custom TestComplete extensions. Thanks.AutomatedQA.TestComplete.CustomControls.dll could not be found with TestComplete 9.31 installWe recently upgraded TestComplete to version 9.31, and I was tasked with ensuring the new version was compatible with our existing Custom Control extensions that are built with the AutomatedQA.TestComplete.CustomControls.dll assembly which we got with the TestComplete 8 SDK. My problem is that I can't find that assembly anywhere with the TestComplete 9 install files. I even installed the TestComplete 10 SDK (as the TestComplete 9 SDK download is nowhere to be found now) to see if it's in the SDK install, but it's not there either. What am I missing?Can a custom TestComplete extension (dll) be installed from a network drive?I created a TestComplete extension using the SDK that provides a few methods that are exposed to TestComplete. When I install the extension from my local drive, everything works just fine and I can see the extension methods in the object browser; however, when I install it from a network drive, I no longer see the extension methods that I saw before. No error or exception occurs, the extension methods are simply not there. I did a test to see if it had to do with permissions. I installed RemoteDLL (http://www.novell.com/coolsolutions/tools/17354.html) and tried manually injecting the extension dll into the running AUT and it succeeded, which leads me to believe that whatever is happening is on TestComplete's end.Re: Clicking a UIA objectFor some reason I can't see my latest reply or yours in the SQA forums thread. I discovered the issue and fixed it. I needed to define the patterns for my custom automation peers. Once the patterns were defined I could see the respective properties/methods in TestComplete. Thanks Tanya.Re: Clicking a UIA objectThanks for the reply Tanya. I've actually solved this issue. I found that the bounds for a UIA object should be screen coordinates and not relative to the current coordinate system. I do however have another question. I've already posted this question on the SqaForums but I have not had a response in about a week. Up until now we have been using Custom Extensions to automate our own custom control but we want to use a better strategy for our future releases. We considered AutomationPeers; however, after investigating TestComplete's UIA objects and the support for AutomationPeers it seems like it doesn't allow for much, if any, customization. "...if your application implements a custom provider exposing specific properties, they will not be available to TestComplete." I got this quote from here: http://support.smartbear.com/viewarticle/30724/. That seems to be true, but it also doesn't seem to be possible to expose any methods or properties in even the standard providers written by Microsoft. The following has been my approach up till now. I have a custom automation peer class that inherits AutomationPeer and implements a standard provider like IScrollItemProvider. In TestComplete I can see the UIA object and all the standard AutomationPeer properties but none of the IScrollItemProvider properties or methods. I understand that a custom provider like ICustomProvider wouldn't work, but why wouldn't the standard ones work? Am I missing something or is this just not supported? Thanks again.Clicking a UIA objectOur AUT has a custom control that is like a grid and manually draws it's cells on a "render surface". These cells are completely custom and do not inherit from any Microsoft library classes (i.e. FrameworkElement). We have a need to automate interactions with this custom control so we decided to look into AutomationPeers. I have tested this approach and TestComplete is able to recognize the custom UIA objects; however, when I try to click one of the cells in this custom grid it simply clicks the middle of the window. The AutomationPeers for these cells override GetClickablePointCore and provide a correct point to be clicked for that object, but it still doesn't click in the right place. Is this a known issue?