Recently, when deploying a asp.net application to IIS7, I have encountered some problems and now summarize the problems and deployment steps encountered in the deployment, this article only involves the basic deployment of asp.net.
One, Deployment Environment
Windows 7 + IIS 7 +asp.net.
Because the test environment is built, so there is no use of the database, some data are put into the list of analog.
Second, Deployment Steps
(1) Enter the Control Panel-> Management tool->internet Information Services (IIS) Manager to enter the IIS Management Server.
(2) Click on the left side of the site-> add site, the following figure:
(3) Add the website fill in the information below, fill out the information, click OK.
[1] "aspdotnetexample" application is we want to deploy the ASP.net application, fill in the physical path only need to fill in the "aspdotnetexample" application of the root application can, see the following figure:
(4) Setting up application pools
(5) Click the "Aspdotnetexample" folder under the "Aspdotnet" website of the new website, right-click "Convert to Application", then click OK directly.
(6) Visit the website, enter in IE
http://127.0.0.1/AspDotNetExample/, you can access the application. where "Aspdotnetexample" is the name of the application, the access effect is as follows:
Third, Deployment Summary
(1) Deployment, when we visit the time when we can not find the namespace of the DLL we developed (the difference between the integration mode and Classic mode), we may use the following several aspects to confirm
[1] DLL is already correctly under "Apply root directory/bin"
[2] As in the 4th step of the previous chapter, do you want to set the application pool to Classic mode rather than integration mode
[3] As in the 5th step of the previous chapter, whether to translate the application folder into an application
(2) Application pool integration mode and Classic mode of difference see article
Http://dev.firnow.com/course/4_webprogram/asp.net/netjs/20100714/445726.html