Summary of website development and debugging methods and summary of website development and debugging

Summary of website development and debugging methods and summary of website development and debugging
Summary of website development and debugging methods website development and debugging VSASP. NET

Debugging is a required skill because VS is often used for development, especially for website development. However, we usually use F5 for debugg debugging. This is actually very inefficient. The following describes a common debugging method.

Preliminary work 1. Build a local IIS Site

First, make sure that you have installed IIS locally. If not. Please refer to this article.
How to install IIS In win7
After the installation is complete, you can build your own developed MVC or Web project into a website.
The procedure is as follows:

1.1 open IIS and right-click "website" to add a website

 

 

1.2 click "select" and select the application pool. Generally, if it is. NET Framework4.0 or later, you can select ASP. NET v4.0. TIPS: You can directly enter the name of the application pool you want to define in the website name. The default value is ASP. NET v2.0. You need to create an application pool and then manually select ASP. NET v4.0 as the integrated version. To facilitate subsequent debugging, you can create a separate application pool.

 

 

1.3 select the physical path and the directory of your project's web site or web project.

 

 

1.4 host name. You can customize a memorable name.

Example: www.aaa.com

My overall configuration is as follows:

 

 

At this time, a website with the local address www.aaa.com has been set up.

2. Use chrome plug-in Host switch plus

For usage, refer to this article:
Hosts proxy plug-in based on Chrome browser
If FQ is unavailable, or github is inaccessible. You can download this attachment:
= Host switch plus

Configure Host switch plus as follows:

 

 

Enable this Configuration:

 

 

Click the icon to change to green.

 

 

In this case, enter www.aaa.com In the chrome browser?
Is it accessible directly?

Debugging

After the IIS Site is used for development, we generally do not need to debug it. If you want to see the effect, just press the access address in the browser.
Even if vs is not started. You can access IIS when it is started.
When you modify the local back-end code, you only need to generate your web project. Refresh the browser to see the effect without interrupting your code.
If you need breakpoint debugging, perform the following operations:
In vs, select "debug" and attach it to the process (shortcut: Ctrl + Alt + P, we recommend using the shortcut key)

 

 

Select iis's process w3wp.exe (enter the letter w to quickly find it) and select the application pool of your IIS Site (the www.aaa.com application pool I used at the time ), select "add" (or press Enter) to debug the breakpoint.