iis-setup

Installing IIS 7 on Windows Vista and Windows 7 

http://www.iis.net/learn/install/installing-iis-7/installing-iis-on-windows-vista-and-windows-7

1. program management


default document
runas /user:administrative_accountname "mmc %systemroot%\system32\inetsrv\iis.msc".


To set up or change the default document

1. In IIS Manager, expand the local computer, expand the Web Sites directory, right-click the designated Web site, and select Properties.
2. Click the Documents tab.
3. Select the Enable default content page check box.
4. Click Add to add a new default document to the list.
5. Click the document you want to remove from the list and click Remove.
6. Click a document from the list and click Move Up or Move down to change the order in which default documents are served to client requests.
7. Click OK.

ASP.NET and IIS 6.0

When running ASP.NET applications on IIS 6.0, it is important to understand how ASP.NET functions when running the two IIS 6.0 application isolation modes. When ASP.NET runs on IIS 4.0, IIS 5.0, or IIS 6.0 in IIS 5.0 isolation mode, it uses its own process model and configuration settings in the Machine.config file. If IIS is running in worker process isolation mode, ASP.NET disables its own process model and utilizes the worker process architecture of IIS 6.0.

The ASP.NET Internet Server API (ISAPI) extension implements a process model that is similar to worker process isolation mode and contains similar worker process management capabilities as the World Wide Web Publishing Service (WWW service). ASP.NET also provides functionality in the form of recycling, health detection, and the ability to force a worker process to have affinity to a particular CPU.

ASP.NET <processModel> Configuration Section

If your ASP.NET application has specific configuration settings in the <processModel> section of the Machine.config file, they will not be used when the application is running in worker process isolation mode, with the exception of maxIOThreads and maxWorkerThreads. IIS reads these configuration values, and sets the following:




maxIOThreads controls the number of threads the worker process uses to receive asynchronous requests from HTTP.sys.
maxWorkerThreads sets the number of application threads in the ASP.NET ISAPI extension.
If developers write applications that have specific <processModel> configurations in ASP.NET other than the values mentioned above, they must be manually converted to the appropriate application pool settings when the application is deployed on IIS 6.0. Additionally, any health detection and recycling features do not automatically transfer over from an ASP.NET configuration to IIS 6.0.

Reroute Requests with Redirects

When a browser requests a page on your Web site, the Web server locates the page identified by the URL and returns it to the browser. When you move a page on your Web site, you can't always correct all of the links that refer to the old URL of the page. To make sure that browsers can find the page at the new URL, you instruct the Web server to give the browser the new URL. The browser uses the new URL to request the page again. This process is called "redirecting a browser request" or "redirecting to another URL." Redirecting a request for a page is similar to using a forwarding address with a postal service. The forwarding address ensures that letters and packages addressed to your original residence are delivered to your new residence.

Redirecting a URL is useful when you are updating your Web site and want to make a portion of the site temporarily unavailable, or when you have changed the name of a virtual directory and want links to files in the original virtual directory to access the same files in the new virtual directory.

Server-Side Includes

Often, it can be useful to dynamically alter Web content after the content has been requested, but before it gets returned to the browser. IIS includes a feature called server-side includes that provides this functionality.

Using server-side includes (SSI), you can carry out a number of of Web site management activities from adding dynamic time stamps to running a special shell command each time a file is requested. SSI commands, called directives, are added to Web pages at design time. When a page is requested, the Web server parses out all the directives it finds in a Web page and then executes them. A commonly used SSI directive inserts, or includes, the contents of a file into a Web page. For example, if you are required to continually update a Web page advertisement, you could use SSI to include the advertisement's HTML source in the Web page. To update the advertisement, you need only modify the file containing the advertisement's HTML source. You do not have to know a scripting language to use SSI; simply follow the correct directive syntax.

ASP and ASP .NET

ASP is a server-side scripting environment that you can use to create dynamic and interactive Web pages, and build powerful Web applications. When the application server receives a request for an ASP file, it processes server-side script code contained in the file to build the HTML Web page that is sent to the browser. In addition to server-side script code, ASP files can contain HTML (including related client-side scripts) as well as calls to COM components that perform a variety of tasks, such as connecting to a database or processing business logic. ASP requires you to use a scripting language, such as VBScript or JScript.

ASP .NET is the next generation of the Microsoft server-side scripting environment. It provides a new programming model and infrastructure, enabling Web developers to build and deploy enterprise-class Web applications that are more secure, scalable, and stable than ever before.