| Like many friends, I usually use editplus when debugging ASP. Of course, I still need to use frontpage for the interface part. I was writing a .net project some time ago and installed VS.net2003. I am going to write an ASP project recently, so I thought about using vs20003 to give it a try. Open VS2003, first create a new project, select Visual Basic project - empty WEB project, the name is webproject1, and then you can see the solution in the resource manager (for VS, not for windows). |
 |
| Click "Project" on the file bar, then click "webproject1 Properties" - "Configuration Properties" - "Debugging", remove "ASP.NET debugging" and turn on "ASP" debugging. |
 |
 |
| Right-click webproject1, add a new item --- WEB form, named index.asp (note that the name is not aspx, but asp). Then you can see the HTML processing editing status of index.asp. |
 |
| Delete all the ready-made codes, because this is automatically generated by VS, and some of the codes are for asp.net. Then you are free to write your ASP pages. When writing code, VS will provide some automatic completion functions, which is very convenient. |
 |
| Now ready to debug. In the resource manager, right-click index.asp and set it as the start page. |
 |
| Then click the "triangle" on the toolbar (haha, it's the play button). This is debugging. |
 |
| Then a window will pop up asking you to enter your local password. Just enter the password of your logged-in user. IE pops up, and the page displays "Debug ASP project under VS". Ha, the debugging was successful! |
 |
| To end debugging, you can click the "square" on the toolbar in VS (to stop debugging), or you can directly turn off IE, which will automatically stop debugging. Okay, let’s talk about some of my experience and understanding. 1. VS is relatively slow to debug ASP programs. This slowness is reflected when opening the IE page, so I recommend that you generally write code and program in VS. When debugging, just open IE for debugging directly as before. However, for complex problems involving process errors, I still like to use single-step debugging in VS, use F9 to set a breakpoint somewhere, and then use F10 to trace, so that the program flow and variable values are all It can be seen very well (for these debugging skills, you can refer to some asp.net books, or previous VS6 books), and it will be much faster to solve complex problems. 2. When creating a new page file, I recommend going directly to the directory, creating it, and then going to the VS resource manager and using Add Existing Item to import it, so that the created file does not have junk code. 3. VS2003 can provide a very good automatic completion function, which everyone can make full use of. 4. VS.net can implement drag-and-drop loading of controls. You can see it in the "Toolbox" on the left - "HTML". Just click on it, hold down the left mouse button and drag it directly to the place you want to add. Since VS.net is for .net, these are also reflected in the attributes of some HTML controls. For example, attributes such as "runat" cannot be used in ASP. However, the properties of most controls are available, and the properties can be conveniently set in the "Design" view. That's all. You can slowly understand it:) Some people say that DW is good, but I have not used it, no. You know what, some people say that DW has a lot of junk code, haha: P |