ASP. NET MVC3 Series Tutorial-Deploy your Web app to IIS 6.0

I:asp.net Pre-work for MVC3 deployment

1. Confirm that the server operating system environment is deployed

First, we confirm that the operating system version of the server can be entered from the System command line tool: SystemInfo Obtaining relevant operating system information for example, then confirm IIS version information, open the IIS Administration Tool, and then confirm the version of the. NET Framework Can be performed on the system command line tool: cd/d%windir%\microsoft.net\framework dir/o

2. Select a deployment scenario

Deployment scenarios Currently, for individuals, will be summarized in 3 scenarios A: Deployment scenarios with source code files (Web Site only) B: Deployment Scenarios without source code files (for Web site/web application) C: Without source code files and ahead of ASP. NET precompiled deployment scenario (for WEB site/web application)

3. Recognize the temporary ASP. NET Files Directory

I'm not sure how many people in this audience know this directory, so I'll simply mention that it won't be long, even if the reader who already knows the catalogue can also look at the basics of memory consolidation! Its location is located in C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP. NET files for storing the page assembly files that were compiled by the ASP. (Note: v4.0.30319 is the. NET version number, specific to the actual situation to make corresponding adjustments!) Code a plain page code. Then the assembly file that was processed by the ASP.

4. Customizing the Temporary ASP. NET Files directory location

Very simple, just modify the configuration of the Web. config.

<System.Web> <CompilationDebug="TrueTargetFramework="4.0 "Tempdirectory="E:\xxx\ "> <Assemblies> <AddAssembly="System.Web.Abstractions, version=4.0.0.0, culture=neutral, publickeytoken=31bf3856ad364e35 "/> <AddAssembly="System.Web.Helpers, version=1.0.0.0, culture=neutral, publickeytoken=31bf3856ad364e35 "/> <AddAssembly="System.Web.Routing, version=4.0.0.0, culture=neutral, publickeytoken=31bf3856ad364e35 "/> <addassembly= "System.Web.Mvc, version=3.0.0.0, Culture=neutral, publickeytoken= 31bf3856ad364e35 " /> <addassembly="System.Web.WebPages, version=1.0.0.0, culture=neutral , publickeytoken=31bf3856ad364e35 " /> </assemblies> </compilation> <!--  .... --></system.web>              

II: Deploy an ASP. MVC3 Application to IIS 6.0

Related Settings for 1.IIS 6.0

In fact, it's very simple. The MVC suffix sets the mapping handler. Make sure that IIS 6.0 can process ASP. NET 4.0 and then set the ASP. NET version to ASP. NET 4.0 for the specific site and then set IIS to direct the ASP. Then set the application extension innuendo last

2. Under load Balancing, remember to set the same machinekey for each Web server, otherwise the view state will not work correctly. The end of this article: Wishing you a happy Mid-Autumn Festival. Precompiled tools, precompiled post-compilation tools

ASP. NET MVC3 Series Tutorial-Deploy your Web app to IIS 6.0