1.What are the different validator controls available in ASP.NET?

Discuss Compare
validator and Range validator in detail.

.NET provides a set of validator controls used to ensure the validity of user input in web
forms before it is processed on the server. These controls are part of the
System.Web.UI.WebControls namespace and are typically used with input controls like
TextBox, DropDownList, etc.
Types of Validator Controls in ASP.NET:
1. RequiredFieldValidator
Ensures that the user does not skip an input field (i.e., the field is not left blank).
2. CompareValidator
Compares the value of one input control with another or with a constant value.
3. RangeValidator
Checks whether the value of a control falls within a specified range.
4. RegularExpressionValidator
Validates the value against a regular expression pattern (e.g., email, phone number).
5. CustomValidator
Enables custom validation logic using server-side or client-side code.
6. ValidationSummary
Displays a summary of all validation errors on a web page.

CompareValidator vs RangeValidator:
Examples:

compare validator:

1.Compares two values

2.Useful for comparing fields like Password and Confirm Passwovalid, NotEqual, Greater Th
an, Less Than, etc.
4.Required (e.g Integer,date ,String)
5.compare against another
CState
l using.

<asp:TextBox ID="txtPassword" runat="server" />

<asp:TextBox ID="txtConfirmPassword" runat="server" />
<asp:CompareValidator
ID="cvPassword"
ControlToCompare="txtPassword"
ControlToValidate="txtConfirmPassword"
Operator="Equal"
Type="String"
ErrorMessage="Passwords do not match"
runat="server" />

RangeValidator:
1.Checks if a value falls within a defined range
2.Useful for numeric or date fields like Age, Price, or Date of Birthday
3.Validates only if the value is within MinimumVa lue and MaximumVa lue
4.Required (e.g., Integer, Double)
5.do not compare against another control using
5.example:
<asp:TextBox ID="txtAge" runat="server" />
<asp:RangeValidator
ID="rvAge"
ControlToValidate="txtAge"
MinimumValue="18"
MaximumValue="60"
Type="Integer"
ErrorMessage="Age must be between 18 and 60"
runat="server" />

2. What do you mean by State Management?

State Management means keeping track of user data when they use a website.
Websites work using HTTP, which is stateless. This means the website does not remember
anything when you go from one page to another. So, if a user enters their name on one
page, the next page won’t remember it — unless we use state management.
ASP.NET gives us tools to remember user data between pages.
Types of State Management:

There are two main types:

1. Client-Side State Management

Data is saved on the user’s browser.

ViewState – Saves data on the same page.
Cookies – Saves small data in the browser.
Hidden Fields – Hidden data inside the form.
Query Strings – Data in the URL.

2. Server-Side State Management

Data is saved on the server.

1.Session State
2.Application State

1.Session State:
Stores data for one user only.
The data is saved on the server.
It lasts until the user closes the browser or is inactive for some time.
Example: Save username when the user logs in.
Session["username"] = "John";
Application State:
Stores data shared by all users.
Data is also saved on the server.
It lasts until the application stops or restarts.
Example: Count total visitors to the website.
Application["visitors"] = 100;

3.Discuss ASP.NET web page life cycle in details.

The ASP.NET Web Page Life Cycle describes the different steps a page goes through from
the time it is requested by a user in a browser until it is sent back and displayed.

These steps help ASP.NET:

1.Process user input,

2.Maintain statraiNET

Handle events,

Render HTML to the browser.

Main Stages of ASP.NET Page Life Cycle:
1. Page Request
The user requests a page (e.g., by typing URL).
ASP.NET checks if the page is already cached or needs to be compiled.
2. Start
Page properties like Request, Response, IsPostBack are set.
Determines if this is the first request or a postback (form submission).
3. Initialization
All controls on the page are initialized.
Unique IDs are assigned to controls.
Settings like themes or master pages are applied.
4. Load ViewState
ViewState data (saved from previous request) is loaded.
Helps remember the values of controls (like TextBox, DropDown) after postback.
5. Load PostBack Data
If it’s a postback, data entered by the user is restored to controls.
6. Load
Page and controls are loaded with data.
You can write your code in Page_Load event.
7. Postback Event Handling
Handles events like button clicks or dropdown changes.
For example, Button1_Click method is called here.
8. Rendering
The page is prepared as HTML.
ASP.NET converts server controls (like <asp:Label>) into HTML (like <span>).
9. Unload
Cleanup happens here (e.g., closing database connections).
Page is unloaded from memory.
5. Explain the Page Events in ASP.NET

When an ASP.NET page runs, it raises several events during its life cycle. These events
allow you (the developer) to write code at different stages of how the page is processed.
Important Page Events (in order):
1. Page_PreInit
First event in the life cycle.
You can:
Set master pages
Set themes
Check if the request is a postback
Example:
protected void Page_PreInit(object sender, EventArgs e)
{
if (!IsPostBack)
{
// Set master page dynamically
this.MasterPageFile = "~/Main.master";
}
}
2. Page_Init
Controls on the page are initialized.
ViewState is not yet loaded.
Good place to:
Create dynamic controls
Example:
protected void Page_Init(object sender, EventArgs e)
{
// Initialize controls here
}
3. Page_InitComplete
Called when initialization is complete.
Useful for tasks that require all controls to be initialized.
4. Page_PreLoad
Called before ViewState is loaded.
Useful for tasks that must run before loading user data.
5. Page_Load
Most commonly used event.
Use it to:
Load data from database
Set control values
Example:
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
// Code runs only first time
 }
}
6. Control Events
Raised after Page_Load.
Includes events like:
Button click (Button1_Click)
Dropdown selection, etc.
Example:
protected void Button1_Click(object sender, EventArgs e)
{
// Handle button click
}
7. Page_LoadComplete
Called after all control events are handled.
Good for post-processing.
8. Page_PreRender
Called just before the page is rendered (converted to HTML).
Good place to make final changes to controls.
9. Page_SaveStateComplete
ViewState is saved.
No changes to controls should be made here.
10. Page_Unload
Final event.
Page is unloaded from memory.
Used for:
Cleconnections
Closing database connection s

Q6. Explain RequiredFieldValidator and RangeValidator with Example.

In ASP.NET, validator controls are used to perform input validation on web forms. They help
to ensure that the data entered by the user is correct and meets the specified criteria before
the form is submitted. Two commonly used validators are:
1. RequiredFieldValidator:
This control is used to make sure the user does not leave a field empty.
It is useful for making fields like Name, Email, Password mandatory.
If the user skips entering the value, an error message is displayed.
Properties:
•ControlToValidate – The ID of the input control to validate.
•ErrorMessage – The message shown if the field is empty.
•ForeColor – Color of the error text.
Example:
<asp:TextBox ID="txtName" runat="server" />
<asp:RequiredFieldValidator
ID="rfvName"
ControlToValidate="txtName"
ErrorMessage="Name is required."
ForeColor="Red"
 runat="server" />
2. RangeValidator:
This control is used to check whether the entered value falls within a specific range.
Useful for fields like Age, Marks, Date, Salary, etc.
It validates numbers, dates, or strings depending on the Type.
Properties:
•ControlToValidate – ID of the control to check.
•MinimumValue – Lower limit.
•MaximumValue – Upper limit.
•Type – Data type (Integer, Double, Date, String).
•ErrorMessage – Message to display if validation fails.
Example:
<asp:TextBox ID="txtAge" runat="server" />
<asp:RangeValidator
ID="rvAge"
ControlToValidate="txtAge"
MinimumValue="18"
MaximumValue="60"
Type="Integer"
ErrorMessage="Age must be between 18 and 60."
ForeColor="Red"
runat="server" />

Q7. What is ViewState? Discuss Page level State management.

ViewState is a method to store values of controls on a web page between postbacks (when
the page reloads after form submission).
It is stored as a hidden field in the web page.
ViewState is a client-side mechanism, meaning the data is saved in the user’s browser.
It is enabled by default for all server controls like TextBox, Label, etc.
Page-level state means storing and managing data within the same page. This data is lost if
the user moves to a different page. ViewState is the main way to manage page-level state.
Techniques for Page-Level State:
1. ViewState – Saves control values across postbacks.
2. Hidden Fields – Saves data in hidden input controls.

Advantages of ViewState:
1.Simple to implement.
2.No server resources needed.
3.Maintains form data between postbacks automatically.
Disadvantages:
1.Increases page size (data stored in HTML).
2.Can slow down performance for large data.
3.Not secure unless encrypted.
Works only on the same page.

8.What is Web Server and Browser? Explain Request and Response Objects.
1. What is a Web Server?
A web server is a software or hardware that stores, processes, and delivers web pages to
users.
It uses HTTP (HyperText Transfer Protocol) to communicate with web browsers.
It receives requests from the client (browser), processes them, and sends back the response
(usually HTML).
Examples of Web Servers:
IIS (Internet Information Services – used with ASP.NET),Apache,Nginx
2. What is a Web Browser?
A web browser is a software application used to access websites and web applications.
It sends requests to web servers and displays the responses as web pages.
Examples of Web Browsers:
Google Chrome,Mozilla Firefox,Microsoft Edge,Safari
3. Request and Response Objects
In ASP.NET, Request and Response are built-in objects that handle communication between
the client (browser) and the server.
A. Request Object (Request)
The Request object is used to get data sent from the browser to the server.
It can read data from:
Form fields (Request.Form)
Query strings (Request.QueryString)
Cookies, headers, and more.
Example:
string name = Request.Form["txtName"];
string id = Request.QueryString["UserID"];
B. Response Object (Response)
The Response object is used to send data from the server back to the browser.
It can be used to:
Display output,
Redirect to another page,
Send files or set cookies.
Example:
Response.Write("Welcome to the website!");
Response.Redirect("HomePage.aspx");

Q9. Explain TreeView and SiteMapPath Navigation Controls

ASP.NET provides navigation controls to help users move between different pages of a
website. Two commonly used navigation controls are:
1.TreeView
2.SiteMapPath

1. TreeView Control
Definition:
TreeView displays a hierarchical structure like a tree.
It is often used for menu navigation, showing folders, categories, etc.
Each item in the tree is called a node.
Features:
Supports expand/collapse nodes.
Can be data-bound to XML files, site maps, or databases.
Used in admin panels, file explorers, category lists, etc.
Example:
<asp:TreeView ID="TreeView1" runat="server">
<Nodes>
<asp:TreeNode Text="Home" NavigateUrl="Home.aspx" />
<asp:TreeNode Text="Products">
<asp:TreeNode Text="Mobiles" NavigateUrl="Mobiles.aspx" />
<asp:TreeNode Text="Laptops" NavigateUrl="Laptops.aspx" />
</asp:TreeNode>
</Nodes>
</asp:TreeView>

2. SiteMapPath Control
Definition:
SiteMapPath is also called a breadcrumb navigation control.
It shows the current location of the user on the website.
Helps users go back to previous pages easily.
Features:
Displays parent and current pages like:
Home > Products > Laptops
Works with SiteMap files (Web.sitemap)
Easy to use and improves website usability.
Example:
<asp:SiteMapPath ID="SiteMapPath1" runat="server" />
Requires SiteMap File:
<siteMap xmlns="http://schemas.microsoft.com/AspNet/SiteMap">
<siteMapNode title="Home" url="Home.aspx">
<siteMapNode title="Products" url="Products.aspx">
<siteMapNode title="Laptops" url="Laptops.aspx"/>
</siteMapNode>
</siteMapNode>
</siteMap>

10.Discuss ADO.NET Connected and Disconnected Architecture

ADO.NET is a data access technology in .NET used to connect to databases, retrieve,

insert, update, and delete data.
It provides two types of architectures to work with data:
1.Connected Architecture
2.Disconnected Architecture

1. Connected Architecture
In Connected Architecture, the application stays connected to the database while performing
operations like reading or writing data.
Example:
SqlConnection con = new SqlConnection("your connection string");
con.Open();
SqlCommand cmd = new SqlCommand("SELECT * FROM Students", con);
SqlDataReader dr = cmd.ExecuteReader();
while (dr.Read())
{
string name = dr["Name"].ToString();
}
dr.Close();
con.Close();

2. Disconnected Architecture
In Disconnected Architecture, the application connects to the database, fetches the data,
and then disconnects. The data is stored in memory (DataSet) and can be used even when
the connection is closed.
Example:
SqlConnection con = new SqlConnection("your connection string");
SqlDataAdapter da = new SqlDataAdapter("SELECT * FROM Students", con);
DataSet ds = new DataSet();
da.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();