In order to take stronger active measures against malicious users and attackers, by default, IIS is not installed on members of the Microsoft Windows Server 2003 family. Moreover, when IIS is initially installed, the service is installed in high security and "locked" mode. By default, IIS is only serving the static content - ie, the ASP, ASP.NET, the server-side containing files, webdav publishing, and FrontPage? Server Extensions only work when enabled. If you do not enable this feature after installing IIS, IIS returns a 404 error. You can provide services for dynamic content and enable these features through the Web service extension node in the IIS Manager. The Windows Server 2003 family provides an enhanced development environment through ASP.NET and IIS integration. ASP.NET identifies most ASP code while providing more features to create an enterprise-level web application, which can work as part of Microsoft .NET Framework. Using ASP.NET allows you 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 is also supported for the latest Web standards (including XML, SOAP, and Internet Protocol version 6.0). This causes everyone to run the APS.NET file directly on 2003. There is an http: // localhost connection, and the page is not open in IIS. It seems that all the webpage to connect to http:// localhost. They can't open, the ASPX file always prompts 404 errors, while other pages can open, this shows that there is no registration APS.NET file (think that it is a way to find online, but there is no solution, relatively depressed. So to Framework Look at the folder, so the file discovers this stuff. The original ASPNET_REGIIS.exe is an ASP.NET IIS Registration Tool. When you perform multiple versions of .NET Framework on a single computer, the script is mapped to the ASP. The ASP.NET ISAPI version of the NET application will determine the version of the public language running library used by the application. ASP.NET IIS Registration Tool (ASPNET_REGIIS.exe) Allows administrators or installers to easily update script mapping of ASP.NET applications to point to the ASP.NET ISAPI version related to the tool. This tool can also be used to display the status of all installed ASP versions. NET registration with the ASP.NET version of the tool pair, create a client script directory, and perform other configuration operations. -I Install the ASP.NET version related to ASPNET_REGIIS.exe and update the IIS configuration database root and its script mapping. Note that only the script mapping of the application using the early ASP.NET version. Using subsequent versions of applications are not affected.
Note When multiple versions of ASP.NET are installed in your computer, ASP.NET will run in parallel. During this installation, Internet Information Services (IIS) needs to know the ASP.NET ISAPI (ASPNET_ISAPI.DLL) version that should be processed in ASP.NET. The ASP.NET ISAPI version associated with the ASP.NET application will determine the public language running library for the application. The ASP.NET application is associated with the ASP.NET ISAPI version via script mapping in IIS. To simplify the configuration process of the ASP.NET application, each ASP.NET version should include a link for the ASPNET_REGIIS.exe version.
Note that each version of .NET Framework contains unique ASPNET_REGIS.EXE versions. Because each version of the tool can only be applied to the .NET Framework version associated with it, use this version of the appropriate tool to configure the ASP.NET application. ASP.NET Installer Microsoft? ASP.NET is installed with Microsoft .NET Framework, Microsoft Visual Studio. Net, and serves as a service on all products of Microsoft Windows® Server 2003 family.
Note that ASP.NET is part of the .NET Framework. You must first install the .NET Framework to install the ASP.NET.
This section describes the necessary steps to install and enable ASP.NET on all platforms that support ASP.NET.
Installing ASP.NET: Describes the Software requirements of ASP.NET and how to install ASP.NET on running Windows Server 2003 family products.
ASP.NET_regiis.exe: Explain how to use the ASP.NET IIS Registration Tool to create script mapping from the application to the ASP.NET specific version and .NET Framework.
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.
Note To install ASP.NET on the domain controller, you must take a special step to make the installation is normal. For more information, see Microsoft Knowledge Base Articles on http://support.microsoft.com Q315158: "ASP.NET cannot use the default ASPNET account on the domain controller."
ASP.NET is installed as part of the .NET Framework version 1.1 as part of Windows Server 2003, you only need to add it as a new program in the control panel, or enable it by using the Configure Your Server wizard.
Note that when using the Configure Your Server Wizard or Add or Remove Programs dialog box on a server running Windows Server 2003, ASP.NET is automatically enabled in the IIS Manager. However, if you are installed by Web or as part of the application (such as Visual Studio .NET), you must manually enable ASP.NET. For instructions, see "Enable ASP.NET" in the IIS Manager running Windows Server 2003 in this topic.
Use the Configure Your Server wizard to install ASP.NET 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. 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. In the Application Server Options dialog box, select the "Enable ASP.NET" check box, click Next, then click Next. If necessary, insert the Windows Server 2003 installation CD into the CD-ROM drive, and then click Next. When the installation is complete, click Finish. Use Add or Remove Programs in Server running Windows Server 2003 to install ASP.NET from the Start menu, point to Control Panel, and then click Add or Remove Programs. In the Add or Remove Programs dialog box, click Add / Remove Windows Components. In the "Components" in the Windows Component wizard, select the Application Server check box, then click Next. When you complete the configuration of Windows Server 2003 in the Windows Component wizard, click Finish. Enable ASP.NET in IIS Manager in the server running Windows Server 2003
From the Start menu, click Run. In the Open box in the Run dialog, type inetmgr, and then click OK. In the IIS Manager, expand your local computer, and then click Web Service Extensions. In the right pane, right-click "ASP.NET" and then click Allow. The state of ASP.NET becomes "allowed".
The parallel support in ASP.NET supports, when updating the component or application on a computer, will delete the old version and replace the newer version. If the new version is not compatible with previous versions, other applications that use this component or application will be interrupted. The .NET Framework provides parallel execution support that allows multiple versions of the assembly or application to be installed simultaneously on the same computer. Since multiple versions can be installed at the same time, the managed application can choose which version to use to avoid affecting other applications using different versions.
In ASP.NET, if the application is installed on the same computer, they use different .NET Framework versions, they can run these applications in parallel. The following topics describe parallel support in ASP.NET and describes how to configure the ASP.NET application to perform in parallel.
I am a beginner, saying is more chaotic, I hope everyone will advise. I also hope that this will have a reference to XDJM encountered in the same problem.
