asp.net environment _windows2003 configured in Win 2003

As you know, Microsoft, in order to better protect against malicious users and attackers, does not install IIS6.0 to members of the Windows Server 2003 family by default. Also, when we initially install IIS6.0, the service is installed in a highly secure and "locked" mode. By default, IIS6.0 only provides services for static content, such as ASP, asp.net, server-side Include files, WebDAV Publishing, and FrontPage server Extensions features that work only when enabled. To install the deployment asp.net environment in Windows 2003 IIS 6.0, let's first look at the new features of IIS6.0 in Windows 2003 How to install IIS6.0 under the server, how to install and deploy the ASP.net environment with IIS6.0, and the relationship between them, the following content will give you a solution.

　　I. New features of IIS6.0

IIS 6.0 includes many new features designed to help businesses, IT pros, and web administrators achieve their goals for performance, reliability, scalability, and security on their Web sites, which may have thousands of sites located on a single IIS6.0 server or multiple servers.

The following table summarizes the important differences between different versions of IIS.

	IIS 4.0	IIS 5.0	IIS 5.1	IIS 6.0
Platform	Windows NT 4.0	Windows 2000	Windows XP Professional	Windows Server 2003 family
Architecture	32-bit	32-bit	32-bit and 64-bit	32-bit and 64-bit
Application process Model	TCP/IP kernel; MTX.exe	TCP/IP kernel; DLLhost.exe (multiple DLL hosts in medium or high application isolation mode)	TCP/IP kernel; DLLhost.exe (multiple DLL hosts in medium or high application isolation mode)	HTTP.sys kernel; When IIS is running in IIS 5.0 isolation mode: Inetinfo.exe (for in-process applications) or DLLhost.exe (for out-of-process applications); When IIS is running in worker process isolation mode: W3wp.exe (multiple worker processes)
Configure Database Configuration	Binary system	Binary system	Binary system	Xml
Security	Windows authentication; SSL	Windows authentication; Ssl;kerberos	Windows authentication; Ssl;kerberos Security Wizard	Windows authentication; Ssl;kerberos Security Wizard; Passport support
Remote Administration	Htmla	Htmla	No HTMLA Terminal Services	Remote Administration Tools (HTML) Terminal Services
Cluster support	In Windows NT 4.0	IIS clusters	Windows Support	Windows Support
WWW Service	IIS on Windows NT 4.0	Personal Web Manager on Windows 9x; IIS on Windows 2000	(optional) IIS on Windows XP Professional	On members of the Windows Server 2003 family

installation of IIS 6.0 server in Windows2003 server

1, use the Configure Your Server Wizard to install IIS6.0

1 From the Start menu, click Manage Your server.
2 under Manage Your server role, click Add or Remove Roles.
3) Read the preliminary steps in the Configure Your Server Wizard, and then click Next.
4 under Server role, click Application Server (iis,asp.net), and then click Next.
5 Read the profile and click Next.
6) Click "Finish".

2. Install IIS, add components, or remove components using the Control Panel

1 From the Start menu, click Control Panel.
2) Double click Add or Remove Programs.
3 Click Add/Remove Windows components.
4 in the Components list box, click Application Server.
5) Click "Details".
6) Click Internet Information Services Manager.
7 Click "Details" to see a list of IIS optional components.
8 Select all optional components to be installed.
9 Click OK until you return to the Windows Components wizard.
10 Click Next, and then complete the Windows Components wizard.

　　 installing ASP.net in Windows 2003 Server

The Windows Server 2003 family uses asp.net and IIS integration to improve the developer experience. asp.net recognizes most ASP code and provides more functionality for creating enterprise-class WEB applications that can work as part of the Microsoft. NET Framework. Using asp.net allows us to take full advantage of the features of the common language runtime, such as type safety, inheritance, language interoperability, and versioning. 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 the services that developers need to create enterprise-class Web applications. Although ASP.net's syntax is essentially ASP-compliant, it also provides a new programming model and infrastructure to improve application security, scalability, and stability. By gradually adding asp.net functionality to existing ASP applications, we are free to make them larger. ASP.net is a compiled, based on. NET environment; we can use any. NET-compatible language, including Microsoft Visual Basic.net,microsoft Visual C # and Microsoft JScript. NET) Authoring applications. In addition, the entire Microsoft. NET Framework is available for any ASP.net application. Developers can easily benefit from these technologies, including the managed common language runtime environment, type safety, inheritance, and so on.

Asp. NET has the following advantages:

1 manageability: ASP.net uses a text-based, hierarchical configuration system that simplifies the work of applying settings to server environments and WEB applications. Because the configuration information is stored as plain text, you can apply the new settings without the help of the local administration tool. Any changes to the configuration file can be automatically detected and applied to the application.
2 Security: ASP.net provides a default authorization and authentication scheme for WEB applications. Developers can easily add, remove, or replace these scenarios, depending on the needs of the application.
3 Easy to deploy: ASP.net applications can be deployed to the server by simply copying the necessary files to the server. You do not need to restart the server, even when you deploy or replace compiled code that is running.
4 Enhanced performance: ASP.net is the compiled code that runs on the server. Unlike traditional Active Server Pages (ASP), asp.net can improve performance with early binding, Just-in-time (JIT) compilation, native, and new caching services.
5 Flexible output caching: ASP.net can cache page data, part of a page, or an entire page, depending on the needs of the application. A cached item can depend on a file or other item in the cache, or it can be refreshed based on an expiration policy.
6 internationalization: ASP.net uses Unicode internally to represent request and response data. You can configure internationalization settings for each computer, per directory, and per page.
7 mobile device Support: ASP.net supports any browser on any device. Developers use the same programming techniques used for traditional desktop browsers to handle new mobile devices.
8 Scalability and Availability: ASP.net is designed to be scalable, with special proprietary functionality to improve the performance of clustered, multiprocessor environments. In addition, Internet Information Services (IIS) and ASP.net run closely to monitor and manage processes so that when an exception occurs in a process, a new process can be created at that location to enable the application to continue processing the request.
9 Tracking and debugging: ASP.net provides a tracking service that can be enabled at both the application level and the page level debugging process. You can choose to view information about the page, or use the application-level trace-viewing tool to view the information. When development and applications are in production, asp.net supports local and remote debugging using the. NET Framework Debugging Tools. When the application is in production state, trace statements can remain in the product code without impacting performance.
10 integration with the. NET Framework: Because ASP.net is part of the. NET Framework, the functionality and flexibility of the entire platform is available to WEB applications. You can also seamlessly access. NET class libraries and messaging and data access solutions from the Web. asp.net is independent of language, so developers can choose the language that is best suited to the application. In addition, the interoperability of the common language runtime also preserves existing investments based on COM development.
11 compatibility with existing ASP applications: ASP and asp.net can run in parallel on the IIS Web server without conflict; There is no possibility that an existing ASP application will crash due to the installation of ASP.net. asp.net only processes files that have an. aspx file name extension. Files with an. asp file name extension continue to be processed by the ASP engine. However, it should be noted that session state and application state are not shared between ASP and ASP.net pages.

Install asp.net

Client and server applications on the Windows Server 2003 family, Windows Professional, server, and Advanced server, and Windows XP Professional support A Sp.net.

A server running a member of the Microsoft Windows Server 2003 family can be configured as an application server and ASP.net as an option that can be enabled when you configure the application server role. To deploy an asp.net Web application to a product server, you must ensure that the asp.net and IIS roles are enabled in the product server before you distribute the application.

1. Use the Configure Your Server Wizard to install ASP.net on a server running Windows Server 2003

1 From the Start menu, click Manage Your server, and in the Manage Your Server window, click Add or Remove Roles.
2 in the Configure Your Server Wizard, click Next, and in the Server Role dialog box, select Application Server (IIS, asp.net), and then click Next.
3 in the Application Server Options dialog box, select the Enable asp.net check box, click Next, and then click Next.
4 Insert the Windows Server 2003 installation CD into your CD-ROM drive if necessary, and then click Next.
5 When the installation is complete, click Finish.

2. Install asp.net using Add or Remove Programs on servers running Windows Server 2003

1 From the Start menu, point to Control Panel, and then click Add or Remove Programs.
2 in the Add or Remove Programs dialog box, click Add/Remove Windows components.
3 in the Windows Components Wizard, in components, select the Application Server check box, and then click Next.
4 When you finish configuring Windows Server 2003 in the Windows Components Wizard, click Finish.

3. Enable ASP.net in IIS Manager in the server running Windows Server 2003

1 From the Start menu, click Run.
2 in the Run dialog box, in the Open box, 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 the asp.net becomes "allowed."

　asp.net the layout of a WEB application

The asp.net application is defined as all files and executables that can be invoked from a virtual directory on a WEB server and its subdirectories. This can include Web pages (. html files), Web Form pages (. aspx files), Web Form user controls (. ascx files), XML Web Services (. asmx files), HTTP handlers, HTTP modules, and other files (such as images and configuration files). All of the script mappings associated with the Microsoft. NET Framework version are now used as part of the ASP.net application. The ASP.net application must be located in the IIS virtual directory (also known as the application root directory). asp.net applications can contain compiled assemblies (typically DLL files that contain business logic), known directories used to store precompiled code (always Bin for directory names), configuration settings stored in text-based, readable web.config files, pages, server controls, and XML WEB Services.

Any precompiled code that is not shared with other applications in the server must be stored in the application's Bin directory. It is the local assembly cache for the application. The Web.config file stores application-level configuration files in an xml-based text file. This means that you can use any standard text editor or XML parser to create them, and they are readable. If you do not include the Web.config file in the application root directory, the configuration settings are determined by the configuration file for the entire server in the Machine.config file. When you install the. NET Framework, a version of the Machine.config file is installed.

The following illustration shows an example of a asp.net application layout.

The applications in this diagram include two DLL files in the Bin directory, a Default.aspx page, a user control named Menu.ascx, an XML Web service named Mywebservice.asmx, and a Global.asax file 。 In addition, the application is configured with the following three configuration files: computer-level machine.config files in the system root, site-level web.config files in the C:inetpubwwwroot directory, and application levels in the application root directory web.config files. When the site's Web.config file overwrites the settings in the Machine.config file, the configuration settings stored in the application root will overwrite the settings in the site's Web.config and machine.config files.

ASP. Comparison between net and IIS, ASP

The relationship between the ASP.net application and Internet information Services (IIS) is as follows: IIS services all requests for a asp.net file that can be published through the aspnet_isapi.dll (asp.net process model). IIS does not process server-side code, while the ASP.net engine processes server-side code and then returns the output to IIS (if possible, or another WEB server).
ASP.net is not just the next generation of ASPs, it provides a new programming model for creating Web applications that use the Internet. Asp. NET and ASP are compared with the following characteristics:

1. Improved performance and scalability

1 Compile and execute: asp.net faster than the traditional ASP, while retaining the ASP "just click Save" Update model. No explicit compilation steps are required. asp.net automatically detects changes, dynamically compiles files as needed, and saves compilation results for subsequent requests to be reused. Dynamic compilation guarantees that the user's application is always up to date, and that the compiled operation will make it run faster. For most applications migrating from traditional ASP to ASP.net, the number of pages processed increased by 3 to 5 times times.
2 large-capacity output caching: ASP.net output caching greatly improves the performance and scalability of the application. When you enable output caching in a page, ASP.net executes the page once and saves the result in memory before it is sent to the user. When other users request the same page, ASP.net uses the cached results in memory to provide services to the user rather than to rerun the page. The output cache is configurable and can be used to cache a single area or an entire page.
3 Web farm Session state: ASP.net session state allows us to share session data between all computers in the Web farm. Users can now access different servers in the Web farm through multiple requests, and still have full access to session data.

2, enhance the reliability

Memory leaks, deadlocks, and fault protection: ASP.net automatically detects errors (for example, deadlocks and memory leaks) and restores them to ensure that our applications are always available. For example, when a memory leak is detected, ASP.net automatically launches a new copy of the ASP.net worker process and directs all new requests to the process. When the old process completes processing of the pending request, it is properly disposed and releases the leaking memory.

3. Simple Deployment

1 "Non-Contact" application deployment: Using ASP.net, we can deploy the entire application by copying it to the server. The configuration settings are stored in the application's XML file.
2 Dynamic Update-running applications: asp.net allows us to update compiled components without restarting the WEB server. Unlike traditional COM components that need to manually restart the Web server after the deployment of an update, ASP.net automatically detects changes and starts with new code.
3 The migration path is simple: asp.net can run on IIS with Microsoft Windows 2000, Windows XP, and members of the Windows Server 2003 family, along with traditional ASP applications. We can migrate one application at a time, even a separate page. ASP.net even allows us to continue using the existing traditional COM business components.

4, the new application model

1 XML Web services: XML Web services allow applications to communicate and share data over the Internet, regardless of operating system and programming languages. ASP.net makes it easier to expose and invoke XML network services.
2 Mobile Web Device support: ASP.net mobile controls allow us to handle more than 80 mobile web devices that use asp.net. We simply write the application once, and the mobile control automatically generates the page requesting the device.

5, the developer's efficiency

1 Simple programming Model: The asp.net of server controls, which allow us to build very good pages with less code than traditional ASP, makes it easier to build real Web applications dynamically.
2 Flexible Language Options: asp.net not only supports Microsoft Visual Basic scripting Edition (VBScript) and Microsoft JScript, but also supports more than 25. NET languages, including for Vi Built-in support for sual Basic. NET, Microsoft C #, and JScript. Net.
3 Rich class Framework: the. NET Framework class Library provides more than 4,500 kinds of classes that encapsulate a large number of features such as XML, data access, file uploads, regular expressions, image generation, performance monitoring and logging, transactions, Message Queuing, and SMTP mail.