How to debug ASP program 70

Select Default in IIS, right-click to open the property and modify the home directory, select the storage path for your ASP file, and change the execution license to a pure script. Application protection is low (IIS process).Then click Application Settings -> click the Configuration button, click the Application tab, and select the Enable Parent Path.

In the document option Set homepage index document , that is, your homepage file, if your homepage file is , if it is not in the enabled default document, you will not be able to automatically open the homepage when you enter the domain name, so we have to add!

You're going to have to put asp** on your own server! Write the local IP address in the address bar!

It must be that your IIS is not set up properly, you see if the directory is wrong, or the read and write permissions of the ** folder are not turned on (especially the database), etc., check it carefully. Most commonly, you don't have an ASP default document (add it to the default document or depending on what your **homepage is).

How to use the asp local debugging tool:

2. Directly put this asp test tool. The exe can be put in the root directory of the **program.,Double-click it directly.。

It will be opened automatically**,If you can't open it,**Click on the home page file name。

Put your debugging tools in your upcoming folder... Then double-click the debugging tool.

The most formal debugging, that is, with the breakpoint debugging function of the system, set the page to be debugged as the start page, and set the breakpoint on the leftmost left machine of the writing **, the steps are as follows:

Press F5, the program enters the debugging page, and there is a yellow arrow on the left, indicating that the program is debugged here. It is important to note here that the yellow phrase has not yet been implemented. The debugging command here notes that f5 indicates the continuation of the execution to the next breakpoint, no matter what is in the middle**, the program is executed sequentially to the next breakpoint.

If there is no breakpoint, then jump directly to the running state.

2.Press f10, which means that a single sentence executes the debugging command, but if you encounter a call function, you will skip the function debugging directly, and if there is a problem with the function, then press f11; If the function is fine, press f10 to skip the debugging of the function. The only difference between f10 and f11 is whether or not to debug functions.

I've only heard of setting the startup page, which page is usually set a breakpoint, and the program will break when it runs there.