![microsoft script debugger ie9 microsoft script debugger ie9](https://docs.microsoft.com/en-us/archive/msdn-magazine/2011/october/images/hh475813.cortifigure5(en-us,msdn.10).png)
Open the dialog and then select the Refresh button in the tools.If your add-in uses the Office Dialog API, the dialog runs in a separate process from the task pane (if any) and the tools must attach to that process. In the add-in, select the Insert button.Set the breakpoints on lines 310 and 312.
![microsoft script debugger ie9 microsoft script debugger ie9](https://venturebeat.com/wp-content/uploads/2019/04/idc-smartphones-q1-2019.png)
In the Debugger tab, open the file Home.js as described in the preceding section.Launch the F12 development tools that corresponds to your version of Office as described in the preceding section.On the Insert tab, in the Add-ins group, select My Add-ins to open the Office Add-ins dialog and then select the STORE tab.
#MICROSOFT SCRIPT DEBUGGER IE9 FREE#
This example uses Word and a free add-in from AppSource. The following screenshot is an example.įor more information about using the F12 tools, see Inspect running JavaScript with the Debugger. When the breakpoint is hit, a right-pointing arrow appears on the red dot of the breakpoint. The following screenshot is an example.Įxecute functions in the add-in as needed to trigger the breakpoint. You'll see a red dot to the left of the line and a corresponding line appears in the Breakpoints tab of the bottom right pane. Scroll to a line where you want to set a breakpoint and click in the margin to the left of the line number. If you're using a transpiler, bundler, or minifier, that changes the name of the file, it will have the final name that is actually loaded, not the original source file name. Select the file that you want to debug and it opens in the the script (left) pane of the Debugger tab.
![microsoft script debugger ie9 microsoft script debugger ie9](http://www.codeproject.com/KB/scripting/UsingVSToDebugJavascript/Scriptdebug2.gif)
Select this to open a drop down list of the files in the add-in. In the upper left of the tab, just below the debugger tool ribbon, there is a small folder icon. This action will attach the F12 tools to the process and open the main F12 user interface. Select your add-in's process that is, its home page file name. The tool cannot attach to processes that are running in other browsers or webviews, including Microsoft Edge. Only processes that are running in Internet Explorer, or Trident, appear. In the following screenshot, it is Home.html. Your add-in will appear in the window named by the filename of the add-in's home page. IEChooser opens with a window named Choose target to debug.
#MICROSOFT SCRIPT DEBUGGER IE9 CODE#
If your add-in has an add-in command that executes a function, the function runs in a hidden browser process that the F12 tools cannot detect or attach to, so the technique described in this article cannot be used to debug code in the function.