Microsoft Dynamics CRM 2011 Scripting Cookbook

Using IE for tracing and debugging

While writing our JScript code, it is highly unlikely that we will always get it right. We could, of course, start throwing alerts and any other type of notifications. The disadvantage to that is the fact that, once we fix the problem, we have to spend the time to go back and clean up the code.

In this recipe we'll be looking at alternative ways to trace our small mistakes.

Getting ready

For the purpose of this recipe, we will not be writing any new code. We'll be using the solution created in the Handling unexpected processing recipe in Chapter 5, Error Handling, and we will be tracing through the execution of those scripts using Internet Explorer and the Developer Tools.

How to do it...

First off, in order to use ...