Hello,
as the original poster didn't give any more information, I'd like to address this problem myself.
I'm trying to automate VS Code with Ranorex 10.5.
When I just call "code" from the command line, I get the cef-chrome-debug-port-used error message when trying to spy on the VS Code window. That's expected.
When I call
then I get the
cef-dom-hwnd-map-window-identification error message. All Ranorex sees is the VSCode Form and inside the form it sees only an Element object named "Chrome Legacy Window". It has an orange exclamation mark in the object tree.
The CEF Plugin properties are:
- DOM pageurl regex black-list: empty String[] Array
- Force win32 rectangle for dom element: false
- Process name black list: String[] Array with two entries: spotify, chrome
- WPF window rule FullType white list: empty String[] Array
I'm pretty sure, that with a previous version of Ranorex I was able to browse the elements inside of (a previous version of) VSCode.