Turn: javascript debugging tool

Today, I saw a good IE Plug-in the blog, which can be used for JavaScript debugging plug-ins in IE6 +, saving us the trouble of writing alert when debugging: javascript debugging tools

Today, it took me a whole day to get the returned value of a linkage menu, 55555 ............

However, the emergence of the problem is always accompanied by a painful determination-I have found a powerful tool for debugging JS: companion. js and Microsoft Script debugger. The following is a reprinted description:

My friends who are doing Web development know that debugging JS programs is quite depressing, because the language syntax is flexible first, and it is a weak type of scripting language, many errors cannot be controlled. The most painful thing is that there are no good debugging tools. The current situation is better than before, and there is firebug in Firefox, this is indeed a good JS debugging tool, but it is very troublesome to use in IE, and the effect is very poor, the monks have been struggling to find a good JS debugging tool under IE, I was able to automatically capture errors and locate the locations and causes. I did not expect that I had accidentally found such a good tool today, so I did not dare to hide it and share it. I hope it will bring convenience to Web developers.

The tool is named companion. JS, please note that this is not a JS file, but a name. It is installed and used as an IE Plug-in and must be used in combination with Microsoft Script debugger. Install this tool, however, when an error occurs on the page, a small error prompt will pop up in the upper left corner. Clicking it will display an error console under IE, just like the firebug console under ff. The error message is detailed.

The following is an example of an error message on the official website:

Address: http://www.my-debugbar.com/wiki/CompanionJS/HomePage

The usage is as follows:
1. Download the Companion. js installation file and then install it.
2. Download and install Microsoft Script debugger. skip this step if your machine has been installed.
3. Open the IE menu "Tools"> "Internet Options"> "advanced" and find "Disable script debugging (Internet Explorer)" and "Disable script debugging (outside Internet Explorer) ", remove all the hooks before the two options, and then restart IE.
4. Enter the "cmdme" link in IE. If a small error message is displayed in the upper left corner or an error message is displayed in the following console, the installation is successful.

Tip: Microsoft Script debugger download to the MS official website (requires the MS operating system genuine verification): http://www.microsoft.com/downloads/details.aspx? Displaylang = ZH-CN & familyid = E606E71F-BA7F-471E-A57D-F2216D81EC3D # filelist or enter Microsoft Script debugger download in Baidu to search for it.

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/E_wsq/archive/2008/09/28/2990952.aspx

Microsoft Script Debugger

Microsoft Script debugger, a script debugging tool that can be used with IE to call the Ajax script code. Use debugger to set breakpoints. After installation, remove "√" before "Internet Options"> "advanced"> "Disable script debugging" (Internet Explorer.
Package: http://files.cnblogs.com/pcjim/Microsoft%20Script%20Debugger.rar

Supplement:
A new example is provided in combination with ie7.0. The test page is An ASPX front-end page containing JavaScript to be tested.
1. When the page to be tested is opened in ie7.0, click View> script debugging program> open. The following window is displayed.

2. Select "new instance of Microsoft Script Debugger"

3. In the checklogin () function, press F9 to set the breakpoint (F8 one-step execution). Click "Log on" on the test page to activate the breakpoint. In the command window, add. value monitoring, because the user name is not lost when the "login" button is pressed, so now monitor lname. value (user name) is empty. As shown in:

Appendix: references on foreign websites (debugging Javascript in your applications)
Http://www.codestore.net/store.nsf/unid/DOMT-5UBUVW

Reproduced to: http://www.cnblogs.com/xuben/archive/2009/12/05/1617810.html

Today, it took me a whole day to get the returned value of a linkage menu, 55555 ............

However, the emergence of the problem is always accompanied by a painful determination-I have found a powerful tool for debugging JS: companion. js and Microsoft Script debugger. The following is a reprinted description:

My friends who are doing Web development know that debugging JS programs is quite depressing, because the language syntax is flexible first, and it is a weak type of scripting language, many errors cannot be controlled. The most painful thing is that there are no good debugging tools. The current situation is better than before, and there is firebug in Firefox, this is indeed a good JS debugging tool, but it is very troublesome to use in IE, and the effect is very poor, the monks have been struggling to find a good JS debugging tool under IE, I was able to automatically capture errors and locate the locations and causes. I did not expect that I had accidentally found such a good tool today, so I did not dare to hide it and share it. I hope it will bring convenience to Web developers.

The tool is named companion. JS, please note that this is not a JS file, but a name. It is installed and used as an IE Plug-in and must be used in combination with Microsoft Script debugger. Install this tool, however, when an error occurs on the page, a small error prompt will pop up in the upper left corner. Clicking it will display an error console under IE, just like the firebug console under ff. The error message is detailed.

The following is an example of an error message on the official website:

Address: http://www.my-debugbar.com/wiki/CompanionJS/HomePage

The usage is as follows:
1. Download the Companion. js installation file and then install it.
2. Download and install Microsoft Script debugger. skip this step if your machine has been installed.
3. Open the IE menu "Tools"> "Internet Options"> "advanced" and find "Disable script debugging (Internet Explorer)" and "Disable script debugging (outside Internet Explorer) ", remove all the hooks before the two options, and then restart IE.
4. Enter the "cmdme" link in IE. If a small error message is displayed in the upper left corner or an error message is displayed in the following console, the installation is successful.

Tip: Microsoft Script debugger download to the MS official website (requires the MS operating system genuine verification): http://www.microsoft.com/downloads/details.aspx? Displaylang = ZH-CN & familyid = E606E71F-BA7F-471E-A57D-F2216D81EC3D # filelist or enter Microsoft Script debugger download in Baidu to search for it.

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/E_wsq/archive/2008/09/28/2990952.aspx

Microsoft Script Debugger

Microsoft Script debugger, a script debugging tool that can be used with IE to call the Ajax script code. Use debugger to set breakpoints. After installation, remove "√" before "Internet Options"> "advanced"> "Disable script debugging" (Internet Explorer.
Package: http://files.cnblogs.com/pcjim/Microsoft%20Script%20Debugger.rar

Supplement:
A new example is provided in combination with ie7.0. The test page is An ASPX front-end page containing JavaScript to be tested.
1. When the page to be tested is opened in ie7.0, click View> script debugging program> open. The following window is displayed.

2. Select "new instance of Microsoft Script Debugger"

3. In the checklogin () function, press F9 to set the breakpoint (F8 one-step execution). Click "Log on" on the test page to activate the breakpoint. In the command window, add. value monitoring, because the user name is not lost when the "login" button is pressed, so now monitor lname. value (user name) is empty. As shown in:

Appendix: references on foreign websites (debugging Javascript in your applications)
Http://www.codestore.net/store.nsf/unid/DOMT-5UBUVW

Reproduced to: http://www.cnblogs.com/xuben/archive/2009/12/05/1617810.html