vscode-edge-devtools
vscode-edge-devtools copied to clipboard
Automatically attach (and open) debugger when debugging (Excel desktop)
There are too many microsoft "guides" on how to set up debugging. Many of which simply does not does not work.
Finally we've gotten debugging to work, but we still need to run our ad-in (from vs code), and then "attach debugger" from the task pane menu. This is extremely tedious after the 100th time.
We're using the Microsoft Edge Tools for VS Code extension but that doesn't attach untill i the above step has been completed. This makes debugging of things like Office.initialize and Office.onReady tricky. I have to run the app, attach debugger, edit code, save and hot-update the app and then hopefully by breakpoint catches. Many times we have to write "debugger;" commandes to even get the debugger to first stop, and then actual breakpoints work.
I would like vs code handle debugging and start immediately when the application runs with no manual "attach debugger" step. With an options to launch the Dev tools in a separate window or debug directly in vs code.
PS.
The IDE's and Documentation for "Office.js" development is not "ready for market".
There are something like 5 different guides on debugging in 5 different places and still we've had to resort to stackoverflow threads to sort things out... really?!
Visual studio has outdated xsd schemas (shared runtime taskpaneappversionoverrides) and VS code does not feel lika a professional develepment tool, nothing works out-of-the box. Extensions are buggy and poorly maintained.
Is your feature request related to a problem? Please describe.
Describe the solution you'd like:
Describe alternatives you've considered:
Additional context:
Apologies about the delay replying, and sorry about the bad experience. I think you would get more useful help by posting in this Q&A channel: https://docs.microsoft.com/en-us/answers/topics/office-addins-dev.html since the issues you encounter are very specific to Office Add-ins. There may be other, better, ways to debug your add-in that the community over there may be able to share.
VS code does not feel lika a professional develepment tool, nothing works out-of-the box. Extensions are buggy and poorly maintained.
Please try to keep your issue descriptions focused on the problem you are encountering. This type of comments do not help move toward a fix.
This has gotten stale and isn't actionable. Closing.