2. File Types managed by ASP.NET
.asax
Typically a Global.asax file that contains code that
derives from the HttpApplication class. This file
represents the application and contains methods
that runs at the start and end of the application
lifetime.
3. File Types managed by ASP.NET
Example Global.asax:
using System;
namespace WebApplication2
{
public class Global : System.Web.HttpApplication
{
void Application_Start(object sender, EventArgs e)
{ }
void Application_End(object sender, EventArgs e)
{ }
void Application_Error(object sender, EventArgs e)
{ }
void Session_Start(object sender, EventArgs e)
{ }
void Session_End(object sender, EventArgs e)
{ }
}
}
4. File Types managed by ASP.NET
.aspx
An ASP.Net Web forms file that contains web form
controls and presentation and business login.
.cd
A class diagram file.
5. File Types managed by ASP.NET
.config
A configuration file (typically Web.config)
containing XML elements that represent settings
for ASP.NET features.
.mdb
An Access database file.
6. File Types managed by ASP.NET
.config Example :
<?xml version="1.0"?>
<configuration>
<connectionStrings>
<appSetting />
</connectionStrings>
<system.web>
<!-- ASP.NET configuration section --!>
</system.web>
</configuration>
7. File Types managed by ASP.NET
.mdf
SQL database file for use with SQL Server Express.
.resources
A resource file that contains resources strings that
refer to images, localizable text or other data.
8. File Types managed by ASP.NET
. browser
A browser definition file used to identify the
features of client browsers.
.sln
A solution file for a Visual Web Developer Project.
9. File Types managed by IIS
.asa
Typically a Global.asax file that contains optional
methods that runs at the start or end of the ASP
session or application lifetime.
.asp
An ASP Web page that contains @ directive and
script code that uses the ASP built-in objects.
10. Static File Types
.css
Style sheet files used to determine the formatting
of HTML elements.
.htm / .html
Static Web files written in HTML code.
11. The Application / Bin Directory
A problem with using the COM model
for Web application components is that those
components must be registered before they can be
used from a traditional ASP application.
registration tool must be run locally on the server.
To make matters more difficult, these components
remain locked on disk once they are loaded by an
application, and the entire Web server must be
stopped before these components can be replaced
or removed.