If Ranorex Studio cannot recognize elements in a .NET WinForms application, review the following possible causes and solutions.
Ranorex and the AUT use different privilege levels
Ranorex tools and the application under test (AUT) must run with the same privilege level.
Close the AUT and all Ranorex tools. Then, restart them using the same privilege level. If the AUT requires administrator privileges, run the Ranorex tools as an administrator as well.
The AUT or test executable runs from a restricted location
Object recognition may be affected when the test executable or AUT is started from a network drive or an encrypted folder.
Copy the executable build and the AUT to a local, non-encrypted folder on the test machine. Then, restart the test from that location.
The application contains obfuscated controls
Ranorex may not be able to identify controls implemented in obfuscated executables.
If possible, test a non-obfuscated build of the application.
The test executable and AUT use different processor architectures
Object recognition may fail when the test executable and AUT target different processor architectures.
Configure the test project to use the same architecture as the AUT:
- In Ranorex Studio, go to Project > Project options > Compiling.
- Configure Target CPU according to the architecture of the AUT:
- For a 64-bit AUT, select Any processor.
- For a 32-bit AUT, select 32-bit Intel-compatible processor.
- Rebuild and run the test again.
For more information, see 64-bit Platforms.