Ranorex handles testing of 32/64 bit based applications on 64 bit operating systems automatically. It is possible, but recommended only for advanced users, to turn off the bit bridge feature within the Ranorex Settings dialog. If you disable the bit bridge feature (not recommended!) or your Ranorex version does not support the bit bridge (versions prior to 2.3), follow the guidelines in this chapter to make 32/64 bit automation interoperable.
On 64 bit versions of Windows, processes may run using 64 bit or 32 bit (also called ‘x86’) architecture. Applications that are started as 32 bit processes are marked with ‘*32’ or ‘(32 bit)’ in the Windows Task Manager, all others use the 64 bit architecture.
Task manager showing 64 and 32 bit calculator applications
Ranorex can run as a 32 bit or 64 bit process, both versions are included in the setup. In general, one should use the Ranorex version that matches the bit architecture of the automated application. I.e. if you automate a 32 bit application, use ‘Ranorex Spy (32bit)’ (formerly ‘Ranorex Spy (x86)’) and ‘Ranorex Recorder (32bit)’ (formerly ‘Ranorex Recorder (x86)’), otherwise use ‘Ranorex Spy’ and ‘Ranorex Recorder’ (64 bit versions).
When you compile your own Ranorex executables, be sure to specify the right target architecture in your project settings. In Ranorex Studio this setting is on the ‘Compiling’ tab in the project properties. .NET applications are by default started as 64 bit processes on 64 bit operating systems unless the target CPU is explicitly set to the 32 bit (x86) architecture. Consequently, set the ‘Target CPU’ property to ‘Any processor’ for automating 64 bit applications and to ’32-bit Intel-compatible processor’ for 32 bit applications.
Ranorex Studio – advanced compiler settings