As you know, Microsoft has a member of the Windows Server 2003 family in order to better prevent malicious users and attackers, by default, no IIS6.0 is installed on the WINDOWS Server 2003 family. Moreover, when we initially install IIS6.0, the service is installed in high security and "lock" mode. By default, IIS6.0 is only serving static content, such as ASP, ASP.NET, in the server-side containment file, WebDAV publishing, and FrontPage Server Extensions feature only work when enabled. Install the ASP.NET environment in Windows 2003 IIS 6.0, we must first learn about the new features of IIS6.0, how to install IIS6.0 under Windows 2003 Server, how we can install and deploy ASP in IIS6.0 The .NET environment, and the relationship between them, the following content will give you a solution. 1. Use "Configuring your Server Wizard" Install IIS6.0 1) From the Start menu, click Manage Your Server. 2) Under Manage Your Server Role, click Add or Remove Role. 3) Read the preparation step in "Configuring your Server Wizard" and click Next. 4) Under Server Roles, click Application Server (IIS, ASP.NET), and then click Next. 5) Read the summary information, then click Next. 6) Click Finish. 2. Use the Control Panel to install IIS, add components or delete components 1) From the Start menu, click Control Panel. 2) Double-click Add or Remove Programs. 3) Click Add / Remove Windows Components. 4) In the Component list box, click Application Server. 5) Click Details. 6) Click Internet Information Services Manager. 7) Click Details to view a list of IIS optional components. 8) Select all optional components to install. 9) Click OK until returns to the Windows Component Wizard. 10) Click Next, then complete the Windows Component Wizard. Third, install the ASP.NET Windows Server 2003 family in Windows 2003 Server uses ASP.NET and IIS integration to improve the developer experience. ASP.NET recognizes most ASP code, and provides more features for enterprise-level web applications that work as part of Microsoft .NET Framework. Using ASP.NET allows us to make full use of the functions of the public language logo, such as type security, inheritance, language interoperability, and version control. IIS 6.0 also provides support for the latest Web standards, including XML, Simple Object Access Protocol (SOAP), and Internet Protocol version 6.0 (IPv6.0). ASP.NET is a unified web development platform that provides developers to create services required by enterprise-level web applications. Although the syntax of ASP.NET is basically compatible with ASP, it also provides a new programming model and infrastructure to improve application security, scaling, and stability.
With the increase in ASP.NET functionality to existing ASP applications, we can freely increase it. ASP.NET is a compiled, based .NET-based environment; we can use any .NET compatible language (including Microsoft Visual Basic.Net, Microsoft Visual C # and Microsoft Jscript .NET) creation applications. In addition, the entire Microsoft .NET Framework can be used for any ASP.NET application. Developers can easily benefit from these technologies, including management of public language runtime environment, type safety, inheritance, etc. The advantages of ASP.NET are as follows: 1) Manageable: ASP.NET uses text-based, graded configuration systems, simplifies how to apply settings to server environments and web applications. Since the configuration information is stored as plain text, you can apply a new setting with help without the local management tool. Any changes to the configuration file can be automatically detected and applied to the application. 2) Safety: ASP.NET provides a default authorization and authentication scheme for web applications. Developers can easily add, delete, or replace them according to the needs of the application. 3) Easy to deploy: ASP.NET application can be deployed to the server by copying the necessary files to the server. You don't need to restart the server, even when you deploy or replace the compiled code, you don't need to restart. 4) Enhanced performance: ASP.NET is the compiled code running on the server. Unlike traditional Active Server Pages (ASP), ASP.NET can use early binding, real-time (JIT) compile, local optimization, and new cache services to improve performance. 5) Flexible Output Cache: ASP.NET can cache some or the entire page of page data, page data, page data, page according to the needs of the application. The cached project can rely on files or other items in the cache, or can be refreshed according to the expiration policy. 6) Internationalization: ASP.NET uses Unicode intern to represent requests and response data. Internationalization can be configured for each computer, each directory, and per page. 7) Mobile device support: ASP.NET supports any browser on any device. Developers use the same programming technology as traditional desktop browsers to process new mobile devices. 8) Scalability and availability: ASP.NET is designed to scale, with specially proprietary functions to improve the performance of the cluster, multiprocessor environment. In addition, Internet Information Services (IIS) and ASP.NET are closely monitoring and managing processes, so that when there is an exception in a process, the new process can be created in this location to continue to process the request. 9) Track and debug: ASP.NET provides a trace service that is enabled during application level and page level debugging. You can choose to view the information of the page, or use the application level tracking view tool to view the information. ASP.NET supports local and remote debugging using the .NET Framework debugging tool when developing and applying in a state of production. When the application is in production, the tracking statement can stay in the product code without affecting performance. 10) Integration with .NET Framework: Because ASP.NET is part of .NET Framework, the functionality and flexibility of the entire platform is available to web applications. The .NET class library and message and data access solution can also be accessed smoothly on the Web. ASP.NET is independent of language, so developers can choose the language that is best suited for the application. In addition, the interoperability of the public language runtime also saves COM-developed existing investments.
11) Compatibility with existing ASP applications: ASP and ASP.NETs can run in parallel in the IIS web server; there is no possibility that the existing ASP application crashes due to installing ASP.NET. ASP.NET only processes files with a .aspx file extension. File with the .asp file extension continues to be processed by the ASP engine. However, it should be noted that the session status and application status are not shared between the ASP and ASP.NET pages. Installing ASP.NET supports ASP.NET on the Windows Server 2003 family, Windows 2000 (Professional, Server, and Advanced Server), and client and server applications on Windows XP Professional. The server running the Microsoft Windows Server 2003 family member can be configured as an application server and an option that can be enabled when configuring the application server role. To deploy an ASP.NET web application to the product server, you must ensure that ASP.NET and IIS roles are enabled in the product server before distributing applications. 1. Install ASP.NET 1 using the "Configure Your Server" wizard to run in the server running Windows Server 2003) From the Start menu, click Manage your Server; in the Manage Your Server window, Click Add or Remove Role. 2) In "Configuring your Server Wizard", click Next, and select the Application Server (IIS, ASP.NET) "in the Server Role dialog box, and then click Next. . 3) In the Application Server Options dialog box, select the Enable ASP.NET check box, click Next, then click Next. 4) If necessary, insert the Windows Server 2003 installation CD into the CD-ROM drive, and then click Next. 5) When the installation is complete, click Finish. 2. Use "Add or Remove Programs" to "Add or Remove Programs" in Server running Windows Server 2003 to point to "Control Panel" from the Start menu, and then click Add or Remove Programs. 2) In the Add or Remove Programs dialog box, click Add / Remove Windows Components. 3) In the "Components" in the Windows Component wizard, select the Application Server check box, and then click Next. 4) When you complete the configuration of Windows Server 2003 in the Windows Component wizard, click Finish. 3. Enable ASP.NET 1 in the IIS Manager running in the server running Windows Server 2003) From the Start menu, click Run.
2) In the Open box in the Run dialog, type inetmgr, and then click OK. 3) In IIS Manager, expand the local computer, and then click Web Service Extensions. 4) In the right pane, right-click "ASP.NET" and then click Allow. The state of ASP.NET becomes "allowed". ASP.NET Web Applications ASP.NET applications are defined as all files and executives that can be called from virtual directories on the web server and their subdirectories. Among them, you can include a web page (.html file), web table page (.aspx file), web form user control (.ascx file), XML Web service (.asmx file), HTTP handler, HTTP module, and other files (such as images) And configuration files). All script maps related to Microsoft .NET Framework now are also part of the ASP.NET application. The ASP.NET application must be in the IIS virtual directory (also known as application root directory). ASP.NET applications can include compiled assemblies (usually a DLL file containing business logic), known directory for storing pre-compilation code (directory name is always bin), stored in text, easy-to-read Configuration settings, pages, server controls, and XML web services in the web.config file. Any precompiled code that is not shared with other applications in the server must be stored in the bin directory of the application. It is a local assembly cache for an application. The web.config file stores the application-level profile in an XML-based text file. This means that any standard text editor or XML analyzer can be used to create them, and they are readable. If you do not contain a web.config file in the application root directory, configure settings to configure the entire server in the machine.config file. When you install .NET Framework, a version of the Machine.config file is installed. The following figure shows an example of the ASP.NET application file system layout. The application in this figure includes two DLL files in the bin directory, a Default.aspx page, a user control called Menu.ascx, an XML web service called MyWebService.asmx and a global.asax file. In addition, the application is configured with the following three configuration files: system root directory Machine.Config file, c: inetpubwwwroot directory, the site level web.config file and application root level Web .config file. When the site's web.config file overrides the settings in the Machine.config file, the configuration settings stored in the application root directory will overwrite the web.config files in the site and the settings in the Machine.config file. Asp.net and IIS, the relationship between the ASP.NET application and the Internet information service (IIS) is as follows: IIS The available ASP.NET file via ASPNET_ISAPI.DLL (ASP.NET process model) All requests provide services. IIS does not handle the code of the server side; the ASP.NET engine processes the server-side code and then returns the output to IIS (if possible, or another web server).
ASP.NET is not just a next-generation ASP, which provides a new programming model for the creation of web applications with Internet. Asp.net and ASP comparisons are as follows: 1. Improved performance and scalability 1) After compiling: ASP.NET is faster than traditional ASP, while retaining ASP "only click Save" update model . There is no need to explicitly compile step. ASP.NET automatically detects change, dynamically compiles files as needed, and saves compilation results for subsequent requests. Dynamic compilation ensures that the user's application is always the latest, and the operation after compiling will make it run faster. For most applications that migrate from traditional ASPs to ASP.NET, the number of pages processed by 3 to 5 times. 2) Large-capacity output cache: ASP.NET output buffer greatly improves the performance and scalability of the application. When an output cache is enabled in the page, the ASP.NET executes this page and saves the results in memory before sending to the user. When other users requested the same page, ASP.NET provides services to users using cache results in memory instead of re-executing the page. The output cache is configurable and can be used to cache a single area or the entire page. 3) Web field session status: ASP.NET session status allows us to share session data between all computers in the web field. Now, users can access different servers in the web field through multiple requests, and still have permissions that fully access session data. 2, enhanced reliability memory leaks, deadlocks and fault protection: ASP.NET automatically detect errors (for example, deadlock and memory leaks) and recovery to ensure that our application is always available. For example, when a memory leak is detected, ASP.NET will automatically start a copy of the new ASP.NET work process and direct all new requests to the process. When the old process completes the processing of the suspend request, it will pass appropriately and release the leaks. 3, deployment simple 1) "Non-contact" application deployment: Using ASP.NET, we can make the entire application to the server by copying it to the server. The configuration settings will be stored in the XML file of the application. 2) Dynamic Update Running Applications: ASP.NET allows us to update the compiled components without restarting the web server. With traditional COM components (these components need to manually restart the web server after deployment updates), ASP.NET automatically detects changes and starts with new code. 3) Simple migration path: ASP.NET can run with traditional ASP applications in Microsoft Windows 2000, Windows XP, and IIS of the Windows Server 2003 family member. We can migrate an app, even a separate page. ASP.NET does even allow us to continue to use existing traditional COM business components. 4, New Application Model 1) XML Web Services: XML Web Services allows applications to communicate and share data over the Internet, regardless of the operating system and programming language. ASP.NET makes it easy to disclose and call XML network services. 2) Mobile Web Device Support: ASP.NET Mobile Control allows us to process more than 80 mobile web devices using ASP.NET. We only need to write applications at once, and the mobile control can automatically generate a page of requesting devices.
