Configuring ASP.Net Environment

in Windows 2003 As we all know, in order to better prevent malicious users and attackers from attacking, Microsoft does not install IIS6.0 to members of the Windows Server 2003 family by default. Moreover, when we initially installed IIS6.0, the service was highly secure and locked.

As we all know, in order to better prevent malicious users and attackers from attacking, Microsoft does not install IIS6.0 by default. On the members of the Windows Server 2003 family. Moreover, when we initially installed IIS 6.0, the service was installed in a highly secure and "locked" mode. By default, IIS 6.0 only serves static content, such as ASP, ASP.NET, server-side include files, WebDAV publishing, and FrontPage Server Extensions, which only work when enabled. In the installation of ASP.net environment in Windows 2003 IIS 6.0, we must first understand the new features of IIS6.0, how to install IIS6.0 under Windows 2003 Server, how to install and deploy ASP under the cooperation of IIS6.0 The .net environment, and the relationship between them, the following content will give you an answer.

I. New Features in IIS6.0

IIS 6.0 includes many new features designed to help businesses, IT professionals and web administrators implement their websites (they) It may have thousands of sites on a single IIS6.0 server or multiple servers) with performance, reliability, scalability, and security goals.

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

Second, Windows2003 Server install IIS 6.0 server

1, the use of " Configure Your Server wizard " install IIS6.0

1) from " Start " Menu, click "Manage your server".

2) in the " manage your server roles " under, click " add or remove roles ".

3) Read the preliminary steps in "Configure your server wizard", then click "Next".

4) in the " server roles " under, click " Application Server (IIS, ASP.NET) ", then click " Next ".

5) Read the summary information and click "Next".

6) Click "Complete".

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 the " Details ".

6) Click "Internet Information Services Manager".

7) Click "Details" to see a list of IIS optional components.

8) Select all the optional components you want to install.

9) Click "OK" until you return to the "Windows Components Wizard".

10) Click "Next", then complete the "Windows Components Wizard".

Third, installing ASP.NET on Windows 2003 Server

The Windows Server 2003 family improves the developer experience with ASP.NET and IIS integration. ASP.NET recognizes most of the ASP code and provides more functionality for creating enterprise-class Web applications that work as part of the Microsoft .NET Framework. Using ASP.NET allows us to take advantage of common language runtime features such as type safety, inheritance, language interoperability, and versioning. IIS 6.0 also supports 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 needed to create enterprise-class Web applications and services. Although the syntax of ASP.NET is basically compatible with ASP, it also provides a new programming model and infrastructure to improve the security, scalability and stability of the application. By gradually adding ASP.NET functionality to existing ASP applications, we are free to increase it. ASP.NET is a compiled, .NET-based environment; we can author applications in any .NET-compatible language, including Microsoft Visual Basic.NET, Microsoft Visual C#, and Microsoft JScript .NET. In addition, the entire Microsoft .NET Framework can be used with any ASP.NET application. Developers can easily benefit from these technologies, including managed common language runtime environments, type safety, inheritance, and more.

The advantages of ASP.NET are as follows:

1) Manageability: ASP.NET uses a text-based, hierarchical configuration system that simplifies the application of settings The server environment and the work of the web application. Because the configuration information is stored as plain text, new settings can be applied without the help of local management tools. Any changes to the configuration file are 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 based 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. There is no need to restart the server, and there is no need to reboot even when deploying or replacing running compiled code.

4) Enhanced Performance: ASP.NET is compiled code that runs on the server. Unlike traditional Active Server Pages (ASP), ASP.NET leverages early binding, real-time (JIT) compilation, native optimization, and new caching services to improve performance.

5) Flexible output caching: Depending on the needs of the application, ASP.NET can cache page data, a portion of a page, or an entire page. Cached items can depend on files or other items in the cache, or can be refreshed according to an expiration policy.

6) Internationalization: ASP.NET uses Unicode internally to represent request and response data. You can configure internationalization settings for each computer, each directory, and each 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 and has special proprietary features to enhance the performance of clustered, multiprocessor environments. In addition, Internet Information Services (IIS) and the ASP.NET runtime closely monitor and manage processes so that when an exception occurs in a process, a new process can be created at that location to allow the application to continue processing requests.

9) Tracking and debugging: ASP.NET provides a tracking service that can be enabled during application level and page level debugging. You can choose to view the information on the page or use the application-level tracking tool to view the information. ASP.NET supports local and remote debugging using the .NET Framework debugging tools while development and applications are in production. When an application is in production, trace statements can remain in the product code without affecting performance.

10) integrated with the .NET Framework: Because ASP.NET is part of the .NET Framework, functionality and flexibility of the entire platform is a Web application usable. The .NET class library and messaging and data access solutions are also easily accessible from the web. ASP.NET is independent of the language, so developers can choose the language that best suits the application. In addition, the interoperability of the common language runtime 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 existing ASP application caused by installing ASP.NET The possibility of a program crash. ASP.NET only processes files with an .aspx file extension. Files with an .asp file 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

In the Windows Server 2003 family, Windows 2000 (Professional, Server and Advanced Server), and client and on the Windows XP Professional Server applications support ASP.NET.

Servers running Microsoft Windows Server 2003 family members can be configured as application servers and have ASP.NET as an option that can be enabled when configuring application server roles. To deploy an ASP.NET Web application to a production server, you must ensure that the ASP.NET and IIS roles are enabled on the production server before distributing the application.