runtimeExecutable is not allowed
janmechtel opened this issue · 3 comments
I'm super excited to attach VS code directly to the Office application (Excel) in my case.
I'm struggling to follow the instructions. I'm under the impression i need to attach to a runnin process so I'm trying to do:
"useWebView": "advanced",
"runtimeExecutable": "C:\\Program Files\\Microsoft Office\\root\\Office16\\Excel.exe",
But `runtimeExecutable" is then yellow underlined as "is not allowed.
When I launch the debugger in a separate insiders instance:
HTTP GET failed: Error: connect ECONNREFUSED 127.0.0.1:9229
There was an error connecting to http://127.0.0.1:2015/json/version : connect ECONNREFUSED 127.0.0.1:9229
I tried the troubleshooting on that from the readme:
http://localhost:2015/json/list
Does't resolve/return anything.
Here is the full launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Attach to Edge",
"port": 9229,
"request": "attach",
"type": "edge",
"webRoot": "${workspaceFolder}",
"useWebView": "advanced",
"runtimeExecutable": "C:\\Program Files\\Microsoft Office\\root\\Office16\\Excel.exe",
"trace": true
},
{
"name": "Attach to Node Functions",
"type": "node",
"request": "attach",
"port": 9229,
"preLaunchTask": "func: host start"
},
]
}
- VS Code Version: 1.53.0-insider
http://localhost:9229/json/list returns something +
Once I changed to launch.json in a separate project folder and used the port 9229, it seems to connect.
Now I'll have to make it use a breakpoint despite the code being in the other instance of code?
So the debugger is attaching now and i can read the debugger log via debug console if I open a separate folder with a launch.json like this:
{
"version": "0.2.0",
"configurations": [
{
"name": "Attach to Edge",
"port": 9229,
"request": "attach",
"type": "edge",
"webRoot": "${workspaceFolder}",
"useWebView": "advanced",
"runtimeExecutable": "C:\\Program Files\\Microsoft Office\\root\\Office16\\Excel.exe",
"trace": true,
}
]
}