442 Project 4 CREATING AN AIRLINE RESERVATION PORTAL

lstMonth.Items.Add(“July”);

lstMonth.Items.Add(“August”);

lstMonth.Items.Add(“September”);

lstMonth.Items.Add(“October”);

lstMonth.Items.Add(“November”);

lstMonth.Items.Add(“December”);

}

After specifying the preceding code, when you run the application and click on the button, the list box is populated with the months of the year.

Configuring ASP.NET Applications

After you create an ASP.NET application, you need to secure it. You also need to ensure that your application can be ported to Web ser vers easily. Therefore, two important features of configuring an ASP.NET application are security and deployment. I will include a brief description of these concepts in this section.

Configuring Security for ASP.NET Applications

ASP.NET applications can be secured at IIS or at the Web application level. The security methods employed at these two levels are described in the following list:

IIS. You can configure application-level security to specify the authentication mode for a Web site or a virtual directory at IIS. You can also configure the file access permissions for the Web site on IIS Server.

ASP.NET. All ASP.NET applications include a Web.Config file that is used for storing the application configuration. You can modify this file for changing the authentication mode of your application, specifying a list of users who are allowed to access your Web site, and specifying the default login page that is displayed when an unauthenticated user requests for a resource that requires authentication. The file-based security mechanism provided by ASP.NET can help implement subdirectory level security for a Web application. For example, you can implement form-based authentication for Web forms in one folder of your application, which is accessible to the registered users on the Web site. You can implement Windows authentication for Web forms in another folder, which is accessible only by corporate employees.