![]() Syntax errors are the most common errors, and the easiest errors to make. Let’s begin by examining the simplest types of errors and then move on to the more difficult ones. The installation procedure won’t create a shortcut on your Start menu. Once you download Microsoft Script Debugger, run the executable file to install the program. Again, keep in mind that there are two versions of the Microsoft Script Debugger: one for Windows 95/98 and one for Windows NT/2000. To find the download, select Script Debugger from the menu and open the Downloads page. Keep in mind that there are two versions of the package: one for Windows 2000 and one for Windows 95/98/NT.įinally, download a copy of the free Microsoft Script Debugger from the Microsoft Scripting Technologies Web site. The Windows Script package includes Windows Script Host 2.0, VBScript 5.5, and JScript 5.5. Just follow the links to the Windows Script Host Downloads section. You can download the Windows Script Host 5.5 package from the Microsoft Windows Script Technologies Web site. Next, you’ll need to have version 2 of the Windows Script Host in order to use some of the debugging techniques that I’ll explain in this Daily Drill Down. Some of the debugging techniques that I’ll show you will take advantage of SynEdit as features to aid in debugging your scripts. I’ll also assume that you have installed and are using SynEdit as your customized Windows Script Host integrated development environment (IDE). In addition, I’ll show you how to use a tool called the Microsoft Script Debugger to aid you in the debugging process.Īs I show you how to debug and test scripts, I’ll assume that you’ve read parts one and two of this tutorial ( “Windows Script Host tutorial: Pseudocode algorithms and other programming basics” and “Creating an integrated development environment for Windows Script Host”). In this Daily Drill Down, I’ll examine the common error conditions in detail, and I’ll describe some techniques that you can use to debug your scripts. Keep in mind that debugging is a skill that will improve as you become more experienced with writing scripts. However, the more you know about the typical error conditions, the easier it will be to troubleshoot or debug them. Tracking down the causes of these errors and resolving them, often referred to as debugging, can be a very tricky procedure. ![]() No matter how careful or experienced you are, it’s a given that some errors will appear in your scripts. The former type of error condition is referred to as a syntax error while the latter can be broken down into two subcategories: runtime errors and logic errors. ![]() These errors can be as simple as misspelling a keyword or forgetting a parenthesis or as complex as an error in how your script performs its job. When you first get started with the Windows Script Host and its scripting languages, chances are that you’ll spend a lot of time tracking down errors in your scripts that prevent them from running correctly. In part three of his Windows Script Host tutorial, Greg Shultz demonstrates how to use several techniques and applications to quickly locate errors in your scripts. ![]() ![]() Windows Script Host tutorial: Debugging and testing your scripts ![]()
0 Comments
Leave a Reply. |