The method and experience of debugging ASP with VS2003

All along, and a lot of friends, I debug the ASP is generally used editplus, of course, the interface part still need to use what FrontPage and so on. Some time ago to write. NET project, installed a vs.net2003, recently to write an ASP project, and then think of using vs20003 to try it. Open VS2003, create a new project, select a Visual Basic project-an empty Web project, a name called Webproject1, and then see the solution in the Resource Manager (vs. not Windows).

The "project" on the point item file Bar, and then point to "Webproject1 properties"--"Configuration Properties"--"Debug", "ASP." NET debugging "Remove, the" ASP "debugging open.

Right-Webproject1, add a new Item---Web Form, named Index.asp (note that the name is not aspx, ASP). You can then see the index.asp HTML processing editing status.

Remove all the ready-made code because this is vs automatically generated, and some of the code is for asp.net. Then you are free to write your ASP page. When writing code, VS will provide some automatic completion functions, very convenient.

Ready to debug now. In Explorer, index.asp, right-click, set to start page.

Then click on the Toolbar "triangle" (haha, is the play button), this is debug debugging.

Then you will jump out of a window to let you enter the local password, you enter the user's password. IE jumped out, the page shows "vs Debug ASP Project", Ha, debugging success!

At the end of debugging, you can click on the "Square" (Stop debugging) in the VS, or you can turn off IE directly, and automatically stop debugging. OK, let's talk about some of my experiences and experience. 1, vs Debugging ASP program is slow, this slow is reflected in the open IE page, so I suggest that the general writing code and programming in VS, debugging time as before, directly open an IE for debugging. However, for complex problems, involving process errors, I prefer to use single step debugging in VS, using F9 to set a breakpoint in a place, and then track with F10, so that for the process of the program, Variable values can be very good to see (these debugging techniques you can refer to a number of asp.net aspects of the book, or the previous VS6 book also do), solve complex problems are much faster. 2, to create a new page file, I suggest or directly into the directory, and then set up, and then to the VS resource Manager, with the Add existing items to import, so that the established file has no spam code. 3, VS2003 can provide a very good automatic completion function, we can make full use of. 4, Vs.net can implement control drag and drop loading, you can in the left of the "toolbox"-"HTML" can be seen, direct point, hold down the mouse left hand directly to the place you want to add. Because Vs.net is for. NET, these are also reflected in the properties of some HTML controls, such as "runat", which cannot be used in ASP. However, most of the properties of CNC components are available, and can be used in the design view of the convenient settings properties well, let's just say so much. We can slowly experience: Some people say that DW is good, I did not use, do not know how, but also some people say DW has a lot of garbage code, OH: P