Ranorex Forum

Is anyone else having problems with visual studio (2005) hanging when debugging ranorex code?

It doesn't happen every time, but enough to be getting annoying. I can't pin it down to a specific operation, it seems more general than that.


Chris

I assume that this "hanging" is caused by setting the Keyboard.AbortKey. If you do not set an abort key, there should not be a delay. Hence comment out the following line:

// Keyboard.AbortKey = System.Windows.Forms.Keys.Pause;

Another cause could be that in your code you subscribed to the Mouse or Keyboard events. That could also cause a hang while debugging.

Regards,
Alex
Ranorex Support Team

I don't set the Abort key anywhere (didn't actually know about it). Most of the "hangs" occurs when not doing mouse or keyboard operations... usually getting properties from objects. When it happens i have to kill VS.

I have also seen same problem. It happens during debugging only sometimes.
Even I have not set Keyboard.AbortKey anywhere and it is also not specific to Mouse or Keyboard events.

Actually, I meant mouse and keyboard events, not actions/operations. That means, hangs could occur if you subscribe to any of the Mouse or Keyboard events, like Mouse.Move or Keyboard.KeyUp.

Could you tell me some more information when those hangs occur? You said they usually happen when you "get properties from objects" - do you mean when you do that in the "watch window" of VS?
Do the hangs occur when you step through the code or when you run the code in the debugger (without a breakpoint)?

Regards,
Alex
Ranorex Support Team

It hangs when stepping through code, usually stepping over a ranorex statement, maybe something like getting the children of an object, or a property of an object.

Unfortunately is does not happen in the same place every time so I can't even provide an example.

The next time I experience the problem I'll make a note of the statement that caused it.


Chris

Just to let everyone else know:
Chris found out that the Visual Studio 2008 hanging problem seems to be a problem with ReSharper 4.5. If ReSharper is enabled, stepping through Ranorex code may bring Visual Studio to hang.

A solution could be to disable ReSharper during debugging, but I don't know if that's possible.

Regards,
Alex
Ranorex Support Team