-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Console Output #20
Comments
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. |
@bgausden did you add "trace": "verbose" to your launch.json config? |
That doesn't affect console output. That allows diagnostic output from the debug extension to be shown. |
I am developing Add-in with Excel, and also encounter this console output problem. If having any solution, please @me. |
@dlee992 install webview2 if you can. I’ve had a better experience with it during development - including debug in the console. |
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?
The text was updated successfully, but these errors were encountered: