search

OfficeDev / vscode-debugger-extension-for-office-addins

VS Code extension to allow for debugging Office Add-ins in VS Code
18 stars 7 forks source link

No Console Output #20

Open bgausden opened 3 years ago

bgausden commented 3 years ago

Windows 20H2 19042.746 Excel 16.0.13707 .20008 64bit

Taken a day of experimentation to understand how to attach the debugger in VS Code. Largely due to my system insisting on using Edge Legacy for webviews.

Now I have breakpoints, I find I don't have any console output in the VS Code Debug Console. Expected?

bgausden commented 3 years ago

I've found a work-around by using the Microsoft Edge DevTools Preview console so not urgent, just extra friction when debugging.

Have also discovered the WebView2 Runtime (https://docs.microsoft.com/en-us/microsoft-edge/webview2/) which does provide console output to the VS Code Debug Console. Missed the requirement that it needed to be separately installed. I'll raise this with the doc project.

TCourtneyOwen commented 3 years ago

@bgausden did you add "trace": "verbose" to your launch.json config?

akrantz commented 3 years ago

That doesn't affect console output. That allows diagnostic output from the debug extension to be shown.

dlee992 commented 3 years ago

I am developing Add-in with Excel, and also encounter this console output problem. If having any solution, please @me.

bgausden commented 3 years ago

@dlee992 install webview2 if you can. I’ve had a better experience with it during development - including debug in the console.