| || |
Detecting nonstandard properties in WPF dialogs
Our developers have added an "AutomationHelper" class to the WPF application (e.g. AutomationHelper.Name), but TestComplete's object spy can't detect it. I can see it in 3rd party tools like WPF inspector.
Is TC's object spy, and TC, in any way extensible in what it can see, possibly by using .AppDomain? Or do I have to make our application "open?"
Re: Detecting nonstandard properties in WPF dialogs
You can access only GUI objects by using the Object Spy, and only they are shown in the object tree. However, WPF applications are always Open, and you can access any objects via native properties and methods of the GUI objects. If none of them return an instance of the target class, you can access it via AppDomain since it should be present in assemblies loaded in your application, and AppDomain provides access to them all. See the "AppDomain Object" help topic and the "Calling .NET Routines via Application Domain" section of the "Calling Functions From .NET Assemblies" help topic.