Exercise 2: Deploying and debugging an Excel Services ECMAScript
In this exercise we will be going over a couple different options to effectively debug your ECMAScript at runtime. This will help you diagnose issues at the source.
Task 1 – Using Internet Explorer 8 for Debugging
In this task we will be taking a look at the IE 8 developer tools that can come in handy when debugging ECMAScript on the fly.
Task 2 – Using a “Logging” Mechanism for Debugging
In this task you will take a look at another method you can use to debug our ECMAScript. This method involves creating functionality within the script itself to relay information about program flow. If you noticed before in FabriKamReporting.js we had a function called writelog() that output information to a Content Editor web part to as events occurred. We can use this function in the same manner across the script to verify the functionality.