Hi!
Thanks for your reply, however this is not our problem.
I think I was not accurate enough with my question. I will try to explain it in more depth.
We have developed our custom solution for automation that leverages Ranorex Api. We use VS2010/Vs2012 for development and TFS for CI and latest version of Ranorex. Basicaly our solution consists of 1 executable and a tonn of Dlls. Those Dlls are containers for test scenarios. Executable project in runtime reflects all of them and extracts all of the test scenarios that are later executed one by one in automatic way. Our test scenarios do heavy usage of GDI plugin. And this system is automatically built by our TFS and uploaded to shared location and later is automatically deployed to virtual machines for execution. So we really do not control the workflow here and changing settings of spy by hand is not an option here. building the solution in x64 mode is not an option as well because we have to support both architectures of product. Testing is performed in such combinations:
1) x64 windows -> x64 product
2) x86 windows -> x86 product
3) x64 windows -> x86 product
Background of a problem:
We have discovered that when using the last combo for tests (specifically on Windows 2003 x64 and 32 bit product) and using 32 bit Spy hangs everything. The Dialog is generic open file dialog and the actual control is a combobox for filename. So when just detecting this control with 32 bit Spy something goes wrong and everything inside OS stops responding. However when using 64 bit Spy on the same combo everything is just fine.
So the question is: Is it possible to force spy 64 bit in runtime programatically on 32 bit version of product?
for example the same way as adding classes to GDI Capture. If yes, how?
Will be very grateful for any help.
Artem.
