I. New features of IIS6.0
IIS 6.0 includes a number of new features designed to help enterprises, IT professionals, and WEB administrators achieve their goals in performance, reliability, scalability, and security by implementing their Web sites (they may have thousands of sites 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|
|System structure||32 Guests||32 Guests||32-bit and 64-bit||32-bit and 64-bit|
|Application process Model||
TCP/IP kernel; MTX.exe
DLLhost.exe (multiple DLL hosts in medium or high application isolation mode)
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 (multi-worker process)|
|Configure Database Configuration||Binary||Binary||Binary||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 Tools (HTML)
|Cluster support||In Windows NT 4.0||IIS Cluster||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|
Ii. Installing the IIS 6.0 server in Windows2003 server
1. Install IIS6.0 using the Configure Your Server Wizard
1) From the Start menu, click Manage Your server.
2) under Manage Your server roles, click Add or Remove Roles.
3) Read the preliminary steps in the Configure Your Server Wizard, and then click Next.
4) Under Server roles, click Application Server (iis,asp.net), and then click Next.
5) Read the summary information, and then click Next.
6) Click "Finish" to download the Deep XP system.
2. Use the Control Panel to install IIS, add components, or remove 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 Components 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 the 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.
III. Installing ASP. NET in Windows 2003 Server
The Windows Server 2003 family has improved the developer experience with ASP. NET and IIS integration. ASP. NET identifies most ASP code and provides more functionality to create an enterprise-class WEB application that works as part of the Microsoft. Using ASP. Allows us to take full advantage of the capabilities 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 the syntax of ASP is basically compatible with ASP, it also provides a new programming model and infrastructure to improve application security, scalability, and stability. by gradually adding ASP. NET functionality to an existing ASP application, we are free to make it larger. ASP. NET is a compiled,,,,,,,,,,,,,,,, and As an application. In addition, the entire Microsoft. NET Framework is available to any ASP. Developers can easily benefit from these technologies, including managed common language runtime environments, 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 tools. Any changes to the configuration file can be automatically detected and applied to the application.
2) Security: ASP. NET provides the default authorization and authentication scheme for the WEB application. Developers can easily add, remove, or replace these scenarios, depending on the needs of the application.
3) Easy to deploy: by simply copying the necessary files to the server, an ASP. NET application can be deployed to that server. You do not need to restart the server, or even when you deploy or replace a running compiled code.
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: Depending on the needs of your application, ASP. NET can cache page data, part of a page, or an entire page. Cached items can depend on files or other items in the cache, or they can be refreshed based on expiration policies.
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) Extensibility and Availability: ASP. NET is designed to be extensible, with special proprietary features to improve the performance of clustered, multiprocessor environments. Additionally, the 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) Tracing and Debugging: ASP. NET provides a tracking service that can be enabled during the application-level and page-level debugging process. You can choose to view the information on the page, or use the application-level tracking view 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 an application is in production, the trace statement can remain in the product code without impacting performance.
10) integration with the. NET Framework: Because ASP. NET Framework is part of, the functionality and flexibility of the entire platform is available to WEB applications. You can also have smooth access to. NET class libraries and messaging and data access solutions from the Web. ASP. NET is independent of the language, so developers can choose the language that best suits the application. Additionally, 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 concurrently on the IIS Web server without conflict; There is no possibility that an existing ASP application will crash due to the installation of ASP. ASP. NET only handles files that have an. aspx file name extension. Files with the. asp file name extension continue to be handled by the ASP engine. However, it should be noted that session state and application state are not shared between ASP and ASP.
Client and server applications on the Windows Server 2003 family, Windows Professional, server and Advanced Server, and on Windows XP Professional support A sp.net win7 system download.
Servers running Microsoft Windows Server 2003 family members can be configured as application servers, 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 Roles 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) If necessary, insert the Windows Server 2003 installation CD into your CD-ROM drive, and then click Next.
5) When the installation is complete, click Finish.
2. Use Add or Remove Programs to install ASP. NET on a server 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 are finished configuring Windows Server 2003 in the Windows Components Wizard, click Finish.
3. Enable ASP. NET in IIS Manager on a 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." and click "Allow". The status of the ASP. NET becomes "Allow" Ghost XP SP3.
Layout of an ASP. NET WEB Application
An ASP. NET application is defined as any file and executable code that can be called 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 script mappings that are currently in use for the Microsoft. NET Framework version are also part of the ASP. The ASP. NET application must reside in the IIS virtual directory (also known as the application root). An ASP. NET application can contain a compiled assembly (typically a DLL file containing business logic), a well-known directory for storing precompiled code (directory name always Bin), configuration settings stored in a text-based, easy-to-read Web. config file, 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 the application-level configuration file in an XML-based text file. This means that any standard text editor or XML parser can be used 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 the 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: The machine-level Machine.config file in the system root, the site-level Web. config file in the C:inetpubwwwroot directory, and the application level in the application root directory Web. config file. When the Web. config file for the site overwrites the settings in the Machine.config file, the configuration settings stored in the application root overwrite the settings in the Web. config file and the Machine.config file.
Asp. NET vs. IIS, ASP
The relationship between an ASP. NET application and Internet Information Services (IIS) is as follows: IIS services all requests for a published ASP. Net file through the Aspnet_isapi.dll (ASP. Process model). IIS does not process server-side code, and 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 ASP, it provides a new programming model for creating Web applications that leverage the Internet. Asp. The features of net vs. asp are as follows:
1. Improved performance and scalability
1) post-compilation: ASP. NET runs faster than traditional ASP, while preserving an ASP "just click to save" update model. No explicit compilation steps are required. ASP. Automatically detects changes, compiles the files dynamically as needed, and saves the compilation results for subsequent requests to be used again. Dynamic compilation ensures that users ' applications are always up-to-date and that the actions performed after compilation make them 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) high-volume output caching: ASP. NET output caching greatly improves the performance and scalability of applications. When output caching is enabled in the page, ASP. NET executes the page once and saves the results 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 serve the user instead of re-executing the page. The output cache is configurable and can be used to cache individual regions or entire pages.
3) Web Farm Session state: The ASP. NET session state allows us to share session data across 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. Enhanced Reliability
Memory leaks, deadlocks, and Fault protection: ASP. NET 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 starts a new copy of the ASP. NET worker process and directs all new requests to the process. When the old process finishes processing the pending request, it passes the appropriate disposition and releases the leaked memory system home.
3. Simple Deployment
1) "Contactless" Application deployment: With ASP., 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 of running applications: ASP. NET allows us to update compiled components without restarting the WEB server. Unlike traditional COM components that require a manual restart of the WEB server after an update is deployed, ASP. NET detects the changes and starts with the new code.
3) Simple migration path: ASP. NET can run on IIS with Microsoft Windows 2000, Windows XP, and Windows Server 2003 family members, 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 existing traditional COM commerce components.
4. 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 language. ASP. NET makes it easier to expose and invoke XML network services.
2) Mobile Web Device Support: The ASP. NET mobile controls allow us to handle more than 80 mobile Web devices that use ASP. We only need to write the application once, and the mobile control will automatically generate the page requesting the device.
5, the efficiency of developers
1) Simple programming Model: Having server controls that allow us to build an extremely effective page with less code than traditional ASP makes it easier to build real Web applications dynamically.
2) Flexible Language options: NET supports not only Microsoft Visual Basic Scripting Edition (VBScript) and Microsoft JScript, but also more than 25. NET languages, including the Vi Sual built-in support for Basic. NET, Microsoft C #, and JScript. Net.
3) Rich class framework: the. NET Framework class Library provides more than 4,500 categories that encapsulate a number of features, such as XML, data access, file uploads, regular expressions, image generation, performance monitoring and logging, transactions, Message Queuing, and SMTP mail.