Obviously I'm spoiled by Chrome and its developer tools, but I'm trying my best to formulate a painless debugging strategy when developing Office 2013 applications using the new JavaScript API for Office.
Visual Studio 2012 helps with a debugging script and an immediate window, but I believe this is a call and you would like pointers / guidance:
Rebooting the Office application (right-clicking “reboot”) interrupts the debugging of the Visual Studio script, so it is often easier to complete debugging and start over. Why does it break? Can I stop his violation?
Is there anything comparable to Chrome's “checking an element” and all the DOM functions associated with it? I use client-side templates (KnockoutJS), and I resort to using the direct window to try to break into the DOM.
My code calls AJAX calls, but apart from the built-in debugging instructions, I haven’t found a way to track calls like the Chrome Network tab.
The three things I have learned / learned that may benefit others are the following:
Do not stop debugging while the debugger stops (is interrupted), as this causes Visual Studio to freeze, and the only way to return is to kill it and restart, which is tedious. If you continue your code until it (I hope) stops, you can stop the debugger without any problems.
Microsoft HTML- . "" , , - . , , . gists table wrapper, , .
"Quick Watch" Visual Studio 2012 jQuery JSON.