Q1 What is ASP.NET? Explain the features of ASP.

NET

AnsASP.NET is a web development platform, which provides a programming model, a

comprehensive software infrastructure and various services required to build up robust web
applications for PC, as well as mobile devices.
ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and policies to set a
browser-to-server bilateral communication and cooperation .
Feature
1. High Performance
Performance is always a critical feature for any of the applications or software. Due to its ASP.NET Core
and Kestrel web server, it’s remarked as the fastest and quick web application framework which is
available in the market. Due to its new Kestrel web server, it is more fast and lightweight. Also, it has
the advantage of asynchronous programming models. All other things like python, java, jsp, php use
an interpreter. However, compilers are faster as compared to the interpreter. Compilers take all the
code and compile at a time. So it is fast because ASP.NET uses compiler-based technology.
2. Cross-Platform and Container Support
As we say it supports cross-platform means it supports Windows, macOS, and Linux. So if we create
ASP.NET application then we can directly deploy it on these platforms.
3. Asynchronous via Async/Await
Asynchronous programming patterns is now implemented in all .net frameworks classes and 3 rd party
libraries. You know why asp.net is faster, because of its wide use of asynchronous patterns in kestrel
frameworks. However, most of the applications spend their lots of time waiting for database queries,
web services call and its input-output operations to complete.
4. Rich Development Environments
If we are creating the application then we will use IDE i.e visual studio. It provides a rich development
environment by which we can easily drag and drop the components (radio buttons, checkboxes, etc.)
and create the application.
5. Language Independent
The framework is language independent that is developers can use various languages like C#. So it’s
easy for a developer to make its application by language which they know. We can create a dynamic
web application using any of the languages.
6. Supports for Web Sockets
Sockets are used to create a client – server-based Applications. By socket normally we can create web-
based client-server applications. These provide back and forth communication of the browser.
7. Action Filters
NET supports a very great feature that is ACTION FILTERS. These filters are used to implement error
handling, authorization, caching or to any custom logic which we would like to implement. There is a
logic been implemented which will be executed before and after controller action. To implement these
logic Action filters are used.
8. Globalization and Localization
We host the web application and it can be accessed from anywhere globally. So language, date and
time format, number format, the currency must be different for different regions or countries. ASP.NET
supports globalization so that different countries’ clients or people also can understand and they can
access this application. ASP.NET customize our application for different languages with the help of
resource files. These files act as a central repository where all the texts are placed.
9. Security

As it supports the .net framework so it will provide security for our application. Applications have its
individual identity, so before running this .net will check its identity of those objects. It will also check
the operating system security. Due to its pre-application configuration and feature of built-in windows
authentication, our developed application is safe and secure. With built-in Windows authentication and
per-application configuration, your applications are safe and secured.

B Explain Ad-Rotator Control.

Ans In ASP.NET, an Ad-Rotator control is a server control that allows developers to easily rotate
and display a sequence of advertisements or images on a web page. This control is particularly useful
for displaying banner ads or promotional content in a rotating manner, providing variety and
potentially increasing user engagement.

Here are the key features and components of the Ad-Rotator control:

AdRotator Server Control: The Ad-Rotator control is a server-side control that is part of the ASP.NET
toolbox. You can drag and drop it onto a web form in the Visual Studio designer, or you can manually
code it in the markup.

Advertisement File: The Ad-Rotator control uses an XML file to store information about the
advertisements, including their image paths, alternate text, URLs, and other relevant details. This file
is specified using the AdvertisementFile property of the control.

1. ERotating Advertisements: The Ad-Rotator control automatically rotates through the

advertisements specified in the XML file. It displays one advertisement at a time and can
transition to the next one based on a defined interval.

2. Customization: Developers can customize the appearance and behavior of the Ad-Rotator
control. For example, you can set properties such as AdvertisementFile, Interval, and
KeywordFilter to control the rotation speed, filter advertisements based on keywords, and
more.

Client-Side Events: The Ad-Rotator control provides client-side events such as AdCreated that allow
developers to write custom JavaScript code to handle specific events when advertisements are created
or displayed.

Q2 A Explain global.asax file.

Ans The Global.asax file is a special file in ASP.NET applications that is used to define application-
level events and global settings. It is also known as the Global Application Class file. The Global.asax
file is automatically detected and executed by the ASP.NET runtime when certain events occur during
the lifecycle of an ASP.NET application.

Here are some key aspects of the Global.asax file:

1. Application Events: The Global.asax file allows you to handle various application-level
events, such as:

 Application_Start: Fired when the application is started for the first time.

 Application_End: Fired when the application is shutting down.

 Session_Start: Fired when a new user session begins.

  Session_End: Fired when a user session ends.

2. Global Settings: You can use the Global.asax file to set global configuration settings for your
application. For example, you might configure custom error handling, authentication, or other
settings that need to be applied at the application level.

3. Global Exception Handling: The Application_Error event in the Global.asax file allows you
to handle unhandled exceptions that occur anywhere in your application. This can be useful for
logging errors or redirecting the user to a custom error page.

4. URL Routing: With ASP.NET MVC applications, the Global.asax file is used to define URL
routing rules, which determine how URLs are mapped to controllers and actions.

<%@ Application Language="C#" %>

<script runat="server">
void Application_Start(object sender, EventArgs e)
{
// Code that runs on application startup
}
void Application_End(object sender, EventArgs e)
{
// Code that runs on application shutdown
}
void Session_Start(object sender, EventArgs e)
{
// Code that runs when a new session is started
}
void Session_End(object sender, EventArgs e)
{
// Code that runs when a session ends
}
void Application_Error(object sender, EventArgs e)
{
// Code that runs when an unhandled error occurs
}
</script>
(b) Explain master page and contents page.
Ans
Master Pages
Master Pages in ASP.NET allow you to create a common layout and content that can be used
consistently across all the pages in a web site. Master Pages can contain HTML Controls, Web
Server Controls, Navigation Controls or Standard controls similar to that of ASP.NET web pages. The
extension of a master page file is .master. The Master page can be easily applied to one or more web
pages in the website. Whenever a change is made in the master page, it automatically reflects across
all the child pages. The master page contains a code-behind file. Code can be written in the code
behind file to handle the various events of the controls placed in the master page. When you create a
master page, it will contain a Master directive as shown below:
<%@ Master
Language="C#"
AutoEventWireup="true"
CodeFile="MasterPage.master.cs"
Inherits="MasterPage"
%>
The Master pages can contain one or more ContentPlaceHolder controls. The ContentPlaceHolder can
be used to insert the markup for the page. The ContentPlaceHolder can contain the content in the
master page or can be used to display the content from the child page. The browser displays the
content inside the ContentPlaceHolder controls. Below is the tag of the ContentPlaceHolder control.
<asp:ContentPlaceHolder
id="ContentPlaceHolder1"
runat="server">
</asp:ContentPlaceHolder>
Content Pages
A content page is the page which uses a master page. The content page contains one or more Content
controls which map to the ContentPlaceHolder controls in the master page. If a content control which
maps to the ContentPlaceHolder in the master page is not available in the content page, then the
content inside the ContentPlaceHolder of the master page is rendered in the content page. The Content
controls can contain HTML Controls, Web Server Controls, or Standard controls similar to that of
ASP.NET web pages. Below is an example of a Content control.
<asp:Content
ID="Content1"
ContentPlaceHolderID="ContentPlaceHolder1"
Runat="Server">
</asp:Content>
Q3 a Explain architecture of ADO.NET
Architecture of ADO.NET :
ADO.NET uses a multilayered architecture that revolves around a few key concepts as –
 asConnection
 Command
 DataSet objects
The ADO.NET architecture is a little bit different from the ADO, which can be shown from the following
figure of the architecture of ADO.NET.
One of the key differences between ADO and ADO.NET is how they deal with the challenge of different
data sources. In ADO.NET, programmers always use a generic set of objects, no matter what the
underlying data source is. For example, if we want to retrieve a record from an Oracle Database, we
use the same connection class that we use to tackle the same task with SQL Server. This is not the
case with ADO.NET, which uses a data provider model and the DataSet.
Features of ADO.NET :
The following are the features of ADO.NET –
 Interoperability-
We know that XML documents are text-based formats. So, one can edit and edit XML
documents using standard text-editing tools. ADO.NET uses XML in all data exchanges and for
internal representation of data.
 Maintainability –
ADO.NET is built around the idea of separation of data logic and user interface. It means that
we can create our application in independent layers.
 Programmability (Typed Programming) –
It is a programming style in which user words are used to construct statements or evaluate
expressions. For example: If we want to select the “Marks” column from “Kawal” from the
“Student” table, the following is the way to do so:
Performance –
It uses disconnected data architecture which is easy to scale as it reduces the load on the database.
Everything is handled on the client-side, so it improves performance.
Scalability –
It means meeting the needs of the growing number of clients, which degrading performance. As it uses
disconnected data access, applications do not retain database lock connections for a longer time. Thus,
it accommodates scalability by encouraging programmers to conserve limited resources and allow
users to access data simultaneously.

b) Explain login control with its different properties

ans In ASP.NET, the Login control is a server control designed to simplify the process of creating a
login page for user authentication. It provides a pre-built user interface for entering credentials
(username and password) and facilitates user authentication against a data store (such as a database).
The Login control is part of the ASP.NET Web Forms framework.
Here are some of the key properties of the Login control:
1. DestinationPageUrl:
  Description: Specifies the URL of the page to which the user is redirected after a
successful login.
 Example:
<asp:Login ID="Login1" runat="server" DestinationPageUrl="~/Welcome.aspx"></asp:Login>
2. FailureText:
 Description: Specifies the text that is displayed when login fails.
 Example:
<asp:Login ID="Login1" runat="server" FailureText="Invalid credentials. Please try
again."></asp:Login>
3. RememberMeSet:
 Description: Indicates whether the "Remember Me" checkbox is checked by default.
 Example:
<asp:Login ID="Login1" runat="server" RememberMeSet="true"></asp:Login>
4. TitleTextStyle:
 Description: Specifies the style for the title text.
 Example:
<asp:Login ID="Login1" runat="server" TitleTextStyle-Font-Bold="true" TitleTextStyle-
ForeColor="Blue"></asp:Login>
5. CreateUserText:
 Description: Specifies the text for the link that navigates to the user registration page.
 Example:
<asp:Login ID="Login1" runat="server" CreateUserText="Register a new account"></asp:Login>
6. LoginButtonText:
 Description: Specifies the text for the login button.
 Example:
<asp:Login ID="Login1" runat="server" LoginButtonText="Sign In"></asp:Login>
7. PasswordRecoveryText:
 Description: Specifies the text for the link that navigates to the password recovery
page.
 Example:
<asp:Login ID="Login1" runat="server" PasswordRecoveryText="Forgot your
password?"></asp:Login>
8. RememberMeText:
 Description: Specifies the text for the "Remember Me" checkbox.
 Example:
<asp:Login ID="Login1" runat="server" RememberMeText="Keep me logged in"></asp:Login>
9. UserNameLabelText:
 Description: Specifies the text for the label associated with the username input field.
 Example:
<asp:Login ID="Login1" runat="server" UserNameLabelText="Username:"></asp:Login>
10. OnAuthenticate:
  Description: Event that occurs when the user attempts to log in. You can handle this
event to customize the authentication logic.
 Example:
<asp:Login ID="Login1" runat="server" OnAuthenticate="Login1_Authenticate"></asp:Login>
In the code-behind file:
Q4 a Explain ASP.NET Page model.

Ans The ASP.NET Page model refers to the programming model that ASP.NET uses for building
dynamic web applications. It defines the structure and behavior of ASP.NET web pages and provides a
set of abstractions and components for creating interactive, data-driven, and scalable web applications.
The Page model is a key aspect of the ASP.NET Web Forms framework, which is one of the web
development frameworks provided by ASP.NET.
Here are the key components and concepts in the ASP.NET Page model:
1. Page Lifecycle:
 Initialization: The page is initialized, and controls on the page are created.
 Load: The page is loaded, and control properties are set.
 Postback Handling: If a postback occurs (e.g., user clicks a button), the page processes
the postback data and events.
 Rendering: The page is rendered, generating HTML that is sent to the client browser.
2. Server Controls:
 ASP.NET provides a rich set of server controls that encapsulate HTML and provide
server-side functionality. Examples include TextBox, Button, GridView, and
DropDownList.
 Server controls have events and properties that can be manipulated on the server side.
3. ViewState:
 ViewState is a mechanism that allows state information to be persisted across postbacks.
It enables controls to maintain their state between requests.
 ViewState is used to store property values of controls, which are then automatically
restored during subsequent requests.
4. Code-Behind Model:
 ASP.NET supports a code-behind model where the HTML markup and server-side code
are separated into two files: the .aspx file (markup) and the .aspx.cs or .aspx.vb file
(code-behind).
 This separation improves maintainability and promotes a clear separation of concerns.
5. Postback Events:
 ASP.NET web pages support postback events, where user actions trigger a round-trip to
the server. Examples include button clicks and dropdown selection changes.
 Event handlers in the code-behind file handle these postback events.
6. Page Directives:
 Page directives are instructions to the ASP.NET runtime and compiler that are placed at
the top of the .aspx file. They use special syntax with the <%@ symbol.
 Examples include the @Page directive, which specifies attributes like Language,
AutoEventWireup, and CodeFile.
 7. ASP.NET Web Forms Controls:
 Web Forms Controls (sometimes called "WebControls") are a set of components that
encapsulate user-interface and other functionality. They include standard controls like
TextBox and Button, as well as complex controls like GridView and DataList.
8. Page Life Cycle Events:
 The Page Life Cycle events, such as Page_Load, Page_Init, Page_PreRender, and others,
allow developers to execute custom code at specific points in the page life cycle.
9. State Management:
 ASP.NET provides various mechanisms for managing state, including ViewState, Session
state, Application state, and more. These mechanisms allow developers to persist and
retrieve data between requests.
Overall, the ASP.NET Page model simplifies web development by abstracting away much of the
complexity involved in handling HTTP requests and responses. It enables developers to build web
applications using a component-based approach, making it easier to create and maintain large-scale
web projects.
b)
Validation Controls in ASP.NET
ASP.NET provides several types of validation controls that can be used to validate user input in web
forms. Some of the common validation controls are:
1. RequiredFieldValidation Control
2. CompareValidator Control
3. RangeValidator Control
4. RegularExpressionValidator Control
5. CustomValidator Control
6. ValidationSummary
The below table describes the controls and their use.
Validation Control Description
RequiredFieldValidation This control ensures that a field is not left empty or blank. It can be used for
textboxes, dropdown lists, checkboxes, and other input controls.
CompareValidator This control compares the value of one input control to another. It can
validate passwords, confirm email addresses, and other scenarios where two
values must match.
RangeValidator This control checks if a value falls within a specific range. For example, it can
be used to validate a user's age, income, or date of birth.
RegularExpressionValida This control checks if a value matches a specified regular expression pattern.
tor For example, it can validate email addresses, phone numbers, zip codes, and
other input types.
CustomValidator This control allows developers to define their validation logic. It usually
depends on the business rules.
ValidationSummary This control displays a report of all validation errors that occurred on a Web
page.
RequiredFieldValidator Control
The RequiredFieldValidator control ensures that the required field is not empty. It is generally tied to a
text box to force input into the text box.
The syntax of the control is as given:
<asp:RequiredFieldValidator ID="rfvcandidate"
runat="server" ControlToValidate ="ddlcandidate"
ErrorMessage="Please choose a candidate"
InitialValue="Please choose a candidate">

</asp:RequiredFieldValidator>
RangeValidator Control
The RangeValidator control verifies that the input value falls within a predetermined range.
It has three specific properties:
Properties Description
Type It defines the type of the data. The available values are:
Currency, Date, Double, Integer, and String.
MinimumValue It specifies the minimum value of the range.
MaximumValue It specifies the maximum value of the range.
The syntax of the control is as given:
<asp:RangeValidator ID="rvclass" runat="server" ControlToValidate="txtclass"
ErrorMessage="Enter your class (6 - 12)" MaximumValue="12"
MinimumValue="6" Type="Integer">

</asp:RangeValidator>
CompareValidator Control
The CompareValidator control compares a value in one control with a fixed value or a value in another
control.
It has the following specific properties:
Properties Description
Type It specifies the data type.
ControlToCompare It specifies the value of the input control to compare with.
ValueToCompare It specifies the constant value to compare with.
Operator It specifies the comparison operator, the available values are:
Equal, NotEqual, GreaterThan, GreaterThanEqual, LessThan,
LessThanEqual, and DataTypeCheck.
The basic syntax of the control is as follows:
<asp:CompareValidator ID="CompareValidator1" runat="server"
ErrorMessage="CompareValidator">
</asp:CompareValidator>
RegularExpressionValidator
The RegularExpressionValidator allows validating the input text by matching against a pattern of a
regular expression. The regular expression is set in the ValidationExpression property.
The following table summarizes the commonly used syntax constructs for regular expressions:
Character Escapes Description
\b Matches a backspace.
\t Matches a tab.
\r Matches a carriage return.
\v Matches a vertical tab.
\f Matches a form feed.
\n Matches a new line.
\ Escape character.
Apart from single character match, a class of characters could be specified that can be matched, called
the meta characters
Q5 a What is state management ? Explain cookies with an example
State management in web development refers to the techniques and mechanisms used to preserve and
manage the state or data of a web application across multiple user requests. Since HTTP, the protocol
used for communication on the web, is stateless, meaning that each request from a client is
independent of previous requests, state management becomes crucial for maintaining user-specific
data or preserving the application's state.
Cookies are one of the methods used for state management. Cookies are small pieces of data sent by a
web server and stored on the user's device. They are sent back to the server with each subsequent
request, allowing the server to recognize and remember the user. Cookies are commonly used for
various purposes, such as tracking user sessions, storing user preferences, and maintaining shopping
cart contents.
Example of Cookies in JavaScript:
Here's a simple example of using cookies in JavaScript to store and retrieve user preferences:
html
Copy code
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Cookie Example</title>
</head>
<body>

<h2>Cookie Example</h2>

<label for="bgColor">Background Color:</label>

<input type="color" id="bgColor">

<label for="fontSize">Font Size:</label>

<select id="fontSize">
<option value="12px">Small</option>
<option value="16px">Medium</option>
<option value="20px">Large</option>
</select>

<button onclick="setPreferences()">Set Preferences</button>

<button onclick="readPreferences()">Read Preferences</button>
 <script>
function setPreferences() {
var bgColor = document.getElementById('bgColor').value;
var fontSize = document.getElementById('fontSize').value;

// Create a cookie with user preferences

document.cookie = "bgColor=" + bgColor + "; expires=Sun, 31 Dec 2023 12:00:00 UTC;
path=/";
document.cookie = "fontSize=" + fontSize + "; expires=Sun, 31 Dec 2023 12:00:00 UTC;
path=/";

alert("Preferences set successfully!");

}

function readPreferences() {
// Read the cookie and retrieve user preferences
var cookies = document.cookie.split(';');
var preferences = {};

for (var i = 0; i < cookies.length; i++) {

var cookie = cookies[i].trim().split('=');
preferences[cookie[0]] = cookie[1];
}

var bgColor = preferences.bgColor || "white";

var fontSize = preferences.fontSize || "16px";

// Apply preferences to the page

document.body.style.backgroundColor = bgColor;
document.body.style.fontSize = fontSize;

alert("Preferences read successfully!");

}
</script>

</body>
</html>
In this example:
The user sets preferences by choosing a background color and font size.
When the "Set Preferences" button is clicked, JavaScript creates cookies to store the selected
preferences.
When the "Read Preferences" button is clicked, JavaScript reads the cookies, retrieves the stored
preferences, and applies them to the page.
It's important to note that this is a basic example using client-side JavaScript. In server-side
technologies, such as ASP.NET or PHP, similar concepts apply, but the server manages cookies.
Cookies can have attributes like expiration date, domain, and path, which determine when and where
they are sent with requests. Additionally, cookies should be used with caution for sensitive data due to
security considerations.
b) Explain tree view control.
Ans
The TreeView control in ASP.NET is a server-side control that allows you to display hierarchical data in
a tree-like structure. It's commonly used to represent relationships between items in a parent-child
hierarchy. The TreeView control provides a user-friendly way to navigate and interact with hierarchical
data.
Key features and concepts related to the TreeView control in ASP.NET:
1. Nodes:
 The fundamental building blocks of a TreeView are nodes. Each node represents an item
in the hierarchy. Nodes can be parent nodes or leaf nodes, and they can have child
nodes.
 You can add nodes declaratively in the markup or programmatically in the code-behind.
2. Parent-Child Relationships:
 Nodes in the TreeView can have parent-child relationships, creating a hierarchical
structure. Child nodes are indented beneath their parent nodes.
3. Populating Nodes Dynamically:
 You can dynamically populate nodes at runtime based on data from a data source or
other criteria. This is often done in response to events or during the Page_Load event.
4. Templates:
 The TreeView control supports templates for nodes, allowing you to customize the
appearance of nodes, including the text, images, and other content.
5. Data Binding:
 You can bind the TreeView control to various data sources, such as XML, databases, or
custom objects. This makes it easy to display dynamic and data-driven hierarchies.
6. Client-Side Events:
 The TreeView control supports client-side events like node click and node
expand/collapse. This enables you to perform client-side scripting to enhance the user
experience.
7. Checkboxes:
 TreeView nodes can include checkboxes, allowing users to select multiple nodes
simultaneously. This is useful in scenarios where users need to make multiple selections.
Here's a simple example of using the TreeView control in ASP.NET:
<asp:TreeView ID="TreeView1" runat="server" ShowCheckBoxes="All">
<Nodes>
<asp:TreeNode Text="Root" Value="root">
<asp:TreeNode Text="Child 1" Value="child1">
<asp:TreeNode Text="Grandchild 1.1" Value="grandchild1.1"></asp:TreeNode>
<asp:TreeNode Text="Grandchild 1.2" Value="grandchild1.2"></asp:TreeNode>
</asp:TreeNode>
<asp:TreeNode Text="Child 2" Value="child2"></asp:TreeNode>
</asp:TreeNode>
</Nodes>
</asp:TreeView>
Q6 Explain SqlDataSource control with different properties
The SqlDataSource control in ASP.NET is a server-side control that simplifies the process of connecting
to a database and retrieving or modifying data. It acts as a bridge between the data source (such as a
SQL Server database) and other data-bound controls like GridView, DetailsView, and FormView.
Here are some of the key properties of the SqlDataSource control:

ConnectionString Property:

Description: Specifies the connection string to the database.

Example:
aspx
Copy code
<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$
ConnectionStrings:MyConnectionString %>" ...></asp:SqlDataSource>
ProviderName Property:
Description: Specifies the ADO.NET data provider for the data source.
Example:
aspx
<asp:SqlDataSource ID="SqlDataSource1" runat="server" ProviderName="System.Data.SqlClient"
...></asp:SqlDataSource>
SelectCommand Property:
Description: Specifies the SQL SELECT statement or stored procedure used to retrieve data.
Example:
aspx
<asp:SqlDataSource ID="SqlDataSource1" runat="server" SelectCommand="SELECT * FROM
Customers" ...></asp:SqlDataSource>
UpdateCommand, InsertCommand, DeleteCommand Properties:
Description: Specifies the SQL statements or stored procedures used to update, insert, or delete
data.
Example:
aspx
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
UpdateCommand="UPDATE Customers SET ContactName = @ContactName WHERE CustomerID =
@CustomerID"
InsertCommand="INSERT INTO Customers (CustomerID, ContactName) VALUES (@CustomerID,
@ContactName)"
DeleteCommand="DELETE FROM Customers WHERE CustomerID = @CustomerID">
</asp:SqlDataSource>
SelectParameters, UpdateParameters, InsertParameters, DeleteParameters Properties:
Description: Specifies the parameters for the corresponding SQL commands. Parameters are used to
pass values dynamically to the SQL statements or stored procedures.
Example:
aspx
<asp:SqlDataSource ID="SqlDataSource1" runat="server">
<SelectParameters>
<asp:Parameter Name="CategoryID" Type="Int32" DefaultValue="1" />
 </SelectParameters>
<UpdateParameters>
<asp:Parameter Name="ProductName" Type="String" />
<asp:Parameter Name="ProductID" Type="Int32" />
</UpdateParameters>
</asp:SqlDataSource>
DataSourceMode Property:
Description: Specifies the mode in which the SqlDataSource control operates. It can be set to DataSet,
DataReader, or DataObject.
Example:
aspx
<asp:SqlDataSource ID="SqlDataSource1" runat="server" DataSourceMode="DataSet"
...></asp:SqlDataSource>
OnSelecting, OnUpdating, OnInserting, OnDeleting Events:
Description: These events allow you to specify event handlers that execute custom logic before the
corresponding SQL operations.
Example:
aspx
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
OnSelecting="SqlDataSource1_Selecting"
OnUpdating="SqlDataSource1_Updating"
OnInserting="SqlDataSource1_Inserting"
OnDeleting="SqlDataSource1_Deleting">
</asp:SqlDataSource>
In the code-behind file:
protected void SqlDataSource1_Selecting(object sender, SqlDataSourceSelectingEventArgs e)
{
// Custom logic before selecting data
}
These properties and events of the SqlDataSource control allow developers to configure database
connectivity, define SQL commands or stored procedures, and customize the behavior of data
operations in an ASP.NET application.
b) Explain login status control.

The LoginStatus control in ASP.NET is a server-side control that is part of the ASP.NET Web Forms
framework. It is typically used in conjunction with the ASP.NET membership and authentication system
to provide a user interface element for user login and logout functionality. The LoginStatus control is
often placed on a master page or any page where you want to display login and logout options to the
user.
Key features and functionalities of the LoginStatus control:
1. Login and Logout Link:
 The LoginStatus control automatically renders as either a "Login" or "Logout" link,
depending on the user's authentication status.
 2. Authentication State Handling:
 The control automatically determines the user's authentication state by checking
whether the user is currently authenticated.
3. Event Handling:
 The control provides server-side events such as LoggingOut, which allows you to execute
custom logic before a user logs out.
4. RedirectURL Property:
 The RedirectURL property allows you to specify a URL to redirect the user to after they
have logged out.
5. Layout Customization:
 You can customize the appearance of the LoginStatus control by using CSS or by setting
various properties such as LogoutAction, LoginText, LogoutText, etc.
Here is a simple example of using the LoginStatus control in an ASP.NET page:
<asp:LoginStatus ID="LoginStatus1" runat="server" LogoutAction="RedirectToLoginPage"
LogoutText="Logout" OnLoggingOut="LoginStatus1_LoggingOut" />
In this example:
 ID: Specifies a unique identifier for the control.
 LogoutAction: Specifies the action to take when the user logs out. In this case, it's set to
"RedirectToLoginPage," which means the user will be redirected to the login page after logging
out.
 LogoutText: Specifies the text to display for the logout link.
 OnLoggingOut: Specifies a server-side event handler that will be called before the user logs out.
In the code-behind file, you can handle the LoggingOut event:
protected void LoginStatus1_LoggingOut(object sender, LoginCancelEventArgs e) { // Custom logic
before the user logs out }
This event handler allows you to execute custom logic before the user logs out, such as clearing
session variables or performing additional cleanup tasks.
The LoginStatus control is a convenient way to provide a consistent user interface for login and logout
functionality in an ASP.NET Web Forms application, especially when using the built-in membership and
authentication system.
Q7 Explain any two HTML Server controls with different properties.
Ans HTML Server Controls in ASP.NET are a set of controls that provide a way to encapsulate HTML
markup and manage them on the server side. Two commonly used HTML Server Controls are
HtmlInputText and HtmlButton.
1. HtmlInputText Control:
The HtmlInputText control represents an HTML <input> element with the type attribute set to "text,"
essentially creating a text input field. It allows users to enter text or numeric values.
Properties of HtmlInputText:
 ID Property:
 Description: Specifies a unique identifier for the control.
 Example:
<input type="text" id="txtUsername" runat="server" />
  Value Property:
 Description: Gets or sets the value of the text input.
 Example:
<input type="text" id="txtUsername" runat="server" value="JohnDoe" />
2. HtmlButton Control:
The HtmlButton control represents an HTML <button> element. It can be used to create buttons that
trigger server-side events when clicked.
Properties of HtmlButton:
 ID Property:
 Description: Specifies a unique identifier for the control.
 Example:
<button id="btnSubmit" runat="server">Submit</button>
 Text Property:
 Description: Gets or sets the text displayed on the button.
 Example:
<button id="btnSubmit" runat="server" text="Submit"></button>
These are just a couple of examples, and there are other properties for each control that allow for
further customization. The runat="server" attribute is crucial for making these controls "server-side"
controls, enabling them to be accessed and manipulated on the server side, in the code-behind files.
These controls provide a convenient way to work with HTML elements while still leveraging the server-
side capabilities of ASP.NET.
b) Explain HTTPResponse object
HTML Server Controls in ASP.NET are a set of controls that provide a way to encapsulate HTML markup
and manage them on the server side. Two commonly used HTML Server Controls are HtmlInputText
and HtmlButton.
1. HtmlInputText Control:
The HtmlInputText control represents an HTML <input> element with the type attribute set to
"text," essentially creating a text input field. It allows users to enter text or numeric values.
Properties of HtmlInputText:
 ID Property:
 Description: Specifies a unique identifier for the control.
 Example:
<input type="text" id="txtUsername" runat="server" />
 Value Property:
 Description: Gets or sets the value of the text input.
 Example:
<input type="text" id="txtUsername" runat="server" value="JohnDoe" />
2. HtmlButton Control:
The HtmlButton control represents an HTML <button> element. It can be used to create buttons
that trigger server-side events when clicked.
Properties of HtmlButton:
 ID Property:
  Description: Specifies a unique identifier for the control.
 Example:
<button id="btnSubmit" runat="server">Submit</button>
 Text Property:
 Description: Gets or sets the text displayed on the button.
 Example:
<button id="btnSubmit" runat="server" text="Submit"></button>
These are just a couple of examples, and there are other properties for each control that allow for
further customization. The runat="server" attribute is crucial for making these controls "server-side"
controls, enabling them to be accessed and manipulated on the server side, in the code-behind files.
These controls provide a convenient way to work with HTML elements while still leveraging the server-
side capabilities of ASP.NET.
Q8 What is Data-Bound Control ? Explain GridView control with different properties.
A Data-Bound Control is a type of control in software development that is connected to a data source,
allowing it to automatically display and manipulate data. These controls simplify the process of working
with data by providing a set of properties, methods, and events specifically designed for data-related
operations.
The GridView control is a data-bound control in ASP.NET used for displaying data in a tabular format. It
is commonly used in web applications to present data from a database or other data source. Here are
some key properties of the GridView control:
1. AutoGenerateColumns: When set to true, the GridView automatically generates columns
based on the data source schema. If set to false, you can manually define the columns.
aspCopy code
<asp:GridView runat="server" AutoGenerateColumns="true" />
2. Columns: This property allows you to manually define the columns when
AutoGenerateColumns is set to false. You can specify the type of column (e.g., BoundField,
CheckBoxField) and set various properties like HeaderText, DataField, etc.
<asp:GridView runat="server" AutoGenerateColumns="false"> <Columns> <asp:BoundField
HeaderText="ID" DataField="ID" /> <asp:BoundField HeaderText="Name" DataField="Name" /> <!--
Add more columns as needed --> </Columns> </asp:GridView>
3. DataSource: This property is used to set the data source for the GridView. You can bind it to a
variety of data sources, such as a DataTable, DataSet, or other data objects.
csharpCopy code
GridView1.DataSource = yourDataSource; GridView1.DataBind();
4. DataKeyNames: Specifies the field or fields that represent the primary key of the data source.
These values can be accessed during events like RowCommand.
<asp:GridView runat="server" DataKeyNames="ID"> <!-- Columns definition --> </asp:GridView>
5. EmptyDataText: Specifies the text to display when the GridView is bound to an empty data
source.
<asp:GridView runat="server" EmptyDataText="No records found"> <!-- Columns definition -->
</asp:GridView>
These are just a few of the many properties of the GridView control. Depending on your specific
requirements, you may need to customize other properties or handle events like RowDataBound,
RowCommand, etc. to achieve the desired functionality.

b) (b) Explain web configuration file.

A configuration file (web.config) is used to manage various settings that define a website. The settings
are stored in XML files that are separate from your application code. In this way you can configure
settings independently from your code. Generally a website contains a single Web.config file stored
inside the application root directory. However there can be many configuration files that manage
settings at various levels within an application.
Usage of configuration file
ASP.NET Configuration system is used to describe the properties and behaviors of various aspects of
ASP.NET applications. Configuration files help you to manage the many settings related to your
website. Each file is an XML file (with the extension .config) that contains a set of configuration
elements. Configuration information is stored in XML-based text files.
Benefits of XML-based Configuration files
 ASP.NET Configuration system is extensible and application specific information can be stored
and retrieved easily. It is human readable.
 You need not restart the web server when the settings are changed in configuration file.
ASP.NET automatically detects the changes and applies them to the running ASP.NET
application.
 You can use any standard text editor or XML parser to create and edit ASP.NET configuration
files.
What Web.config file contains?
There are number of important settings that can be stored in the configuration file. Some of the most
frequently used configurations, stored conveniently inside Web.config file are:
 Database connections
 Caching settings
 Session States
 Error Handling
 Security