I recently deployed an ASP. NET application to iis7, encountered some problems, now the problems encountered in the deployment and deployment steps are summarized, this article only involves ASP.. net.
I,Deployment Environment
Windows 7 + IIS 7 + ASP. NET.
Because the test environment is being set up, the database is not used, and some data is simulated in the list.
II,Deployment steps
(1) Go to Control Panel> Administrative Tools> Internet Information Service (IIS) manager and go to the IIS management server.
(2) Click "website on the left"> "add Website", for example:
(3) Add the website as follows. after entering the information, click OK.
[1] The "aspdotnetexample" application is the ASP. NET application to be deployed. when entering the physical path, you only need to enter the root application of the "aspdotnetexample" application. For details, see:
(4) set the application pool
(5) Click the "aspdotnetexample" folder under the newly created website "aspdotnet", right-click "convert to application", and then click "OK.
(6) access the website and enter
Http: // 127.0.0.1/aspdotnetexample/to access the application. "Aspdotnetexample" is the application name. The access effect is as follows:
III,Deployment Summary
(1) During deployment, when we access the service, the namespace contained in the DLL cannot be found (the difference between the integration mode and the classic mode ), we can confirm through the following aspects:
[1] whether the DLL is in the correct "application root directory/bin"
[2] As shown in step 1 of the previous chapter, do you want to set the application pool to the classic mode instead of the integration mode?
[3] As shown in step 1 of the previous chapter, whether to convert the application folder into an application
(2) differences between the application pool integration mode and the classic mode can be found in the article
Http://dev.firnow.com/course/4_webprogram/asp.net/netjs/20100714/445726.html