ASP.NET Advanced Features

✅ Web Parts in ASP.NET

🔷 What are Web Parts?

Web Parts are a set of customizable controls in ASP.NET that allow users to personalize, modify, and customize the content, appearance, and behavior of Web pages directly from the browser.

Think of them like widgets on a dashboard that users can move, hide, edit, or configure.

🔷 Key Features

🧩 Modular UI: Web page content is divided into blocks (Web Parts)
🎨 Personalization: Users can rearrange, hide, or edit Web Parts
🔄 Dynamic Layout: Drag-and-drop interface for arranging parts
🛠️ Edit Mode: Switch between display, design, and edit modes
📦 Storage: Personalized settings are saved per user (via cookies, database, etc.)

🔷 Components of Web Parts

Component	Description
`WebPartManager`	Central controller for Web Part behavior on a page
`WebPartZone`	A container zone that holds Web Parts
`WebPart`	The actual modular control (e.g., a calendar, news feed, form)
`EditorZone`	Contains editing controls for Web Parts
`CatalogZone`	Provides a catalog of available Web Parts to add
`ConnectionsZone`	Allows Web Parts to share data

🔷 Modes of WebPartManager

Mode	Purpose
`BrowseDisplayMode`	Normal view mode
`DesignDisplayMode`	Allows drag-and-drop
`EditDisplayMode`	Allows property editing
`CatalogDisplayMode`	Allows adding/removing Web Parts
`ConnectDisplayMode`	Allows linking Web Parts

🔷 Example: Simple Web Part Page

📄 ASPX Page

<asp:WebPartManager ID="WebPartManager1" runat="server" />

<asp:WebPartZone ID="WebPartZone1" runat="server">
    <ZoneTemplate>
        <asp:Calendar ID="Calendar1" runat="server" Title="My Calendar" />
        <asp:Label ID="Label1" runat="server" Text="Hello, Web Parts!" Title="Greeting Label" />
    </ZoneTemplate>
</asp:WebPartZone>

<asp:EditorZone ID="EditorZone1" runat="server">
    <ZoneTemplate>
        <asp:AppearanceEditorPart ID="AppearanceEditorPart1" runat="server" />
        <asp:BehaviorEditorPart ID="BehaviorEditorPart1" runat="server" />
    </ZoneTemplate>
</asp:EditorZone>

<asp:DropDownList ID="ddlModes" runat="server" AutoPostBack="true" OnSelectedIndexChanged="ddlModes_SelectedIndexChanged">
    <asp:ListItem Text="Browse" Value="Browse" />
    <asp:ListItem Text="Design" Value="Design" />
    <asp:ListItem Text="Edit" Value="Edit" />
</asp:DropDownList>

📄 Code-Behind (C#)

protected void ddlModes_SelectedIndexChanged(object sender, EventArgs e)
{
    string selectedMode = ddlModes.SelectedValue;

    switch (selectedMode)
    {
        case "Browse":
            WebPartManager1.DisplayMode = WebPartManager.BrowseDisplayMode;
            break;
        case "Design":
            WebPartManager1.DisplayMode = WebPartManager.DesignDisplayMode;
            break;
        case "Edit":
            WebPartManager1.DisplayMode = WebPartManager.EditDisplayMode;
            break;
    }
}

🔷 Personalization

ASP.NET stores each user’s changes using:

Profile Provider (SQL Server)
Cookie-based storage
Allows restoring layout in future sessions

🔷 Advantages

Benefit	Description
✅ User Customization	Each user can personalize their view
🔄 Dynamic Layout	Rearranged via drag-and-drop
🔧 Editable	Properties like font, color, title can be edited
🔌 Modular Design	Easy to maintain or update each module
🔐 Security	You can control who can modify what

🔷 Real-Life Use Cases

📰 Personalized dashboards (e.g., SharePoint)
📊 Interactive analytics pages
🗂 Customizable admin panels
🧾 User-specific content (e.g., news, weather)

✅ Summary

Web Parts offer a modular, customizable user interface.
Managed by WebPartManager, laid out in WebPartZones.
Enable personalization, editing, and dynamic layout without changing server code.
Useful in portal-like applications and dashboards.

✅ ASP.NET Configuration

🔷 What is ASP.NET Configuration?

ASP.NET Configuration refers to the settings and parameters used to define how an ASP.NET application behaves. These settings control things like:

Authentication & Authorization
Custom Errors
Session & State Management
Debugging Options
Database Connections
Security & Performance

🛠 All configuration settings are stored in special XML files — primarily the web.config file.

🔷 Main Configuration Files

File	Description
`web.config`	Application-level configuration file. Each ASP.NET app has its own.
`machine.config`	Global configuration file for all ASP.NET applications on the server.

📝 web.config settings override machine.config settings.

🔷 Structure of `web.config`

<configuration>
  <appSettings>
    <add key="AppName" value="My Website" />
  </appSettings>

  <connectionStrings>
    <add name="MyDb" connectionString="..." />
  </connectionStrings>

  <system.web>
    <authentication mode="Forms">
      <forms loginUrl="login.aspx" timeout="30" />
    </authentication>

    <authorization>
      <deny users="?" />
      <allow users="*" />
    </authorization>

    <customErrors mode="On" defaultRedirect="error.aspx" />
    <compilation debug="true" />
    <sessionState mode="InProc" timeout="20" />
  </system.web>
</configuration>

🔷 Important Configuration Sections

🔹 1. `<appSettings>`

Stores custom key-value pairs used by the app.

<appSettings>
  <add key="Theme" value="DarkMode" />
</appSettings>

🔹 2. `<connectionStrings>`

Stores DB connection strings securely.

<connectionStrings>
  <add name="MyDB" connectionString="Data Source=.;Initial Catalog=Test;Integrated Security=True" />
</connectionStrings>

🔹 3. `<system.web>`

Main section for core settings.

Some sub-sections include:

Tag	Purpose
`<authentication>`	Configure login mechanism (Forms, Windows, etc.)
`<authorization>`	Define access rules (who can access what)
`<customErrors>`	Define custom error pages
`<compilation>`	Enable/disable debugging
`<sessionState>`	Configure session timeout and mode

🔹 4. `<customErrors>`

Customizes what users see on error.

<customErrors mode="On" defaultRedirect="ErrorPage.aspx" />

🔹 5. `<trace>` and `<compilation>`

Helpful during development.

<trace enabled="true" />
<compilation debug="true" />

🔷 Multiple `web.config` Files

You can have multiple web.config files — one at root level, and others in subdirectories.
Settings in deeper folders override parent folder settings.

🔷 How to Edit Configuration

Using Visual Studio (Properties > Configuration)
Manually editing web.config
Using IIS Manager for certain settings (e.g., authentication)

🔷 Security Tip

Never expose sensitive data like passwords directly in web.config. Use encryption:

aspnet_regiis.exe -pef "connectionStrings" "C:\MyApp"

✅ Summary

ASP.NET Configuration is done using XML-based files (web.config).
It allows customization, security, and control of application behavior.
Major sections include settings for auth, session, errors, compilation, and connection strings.
Config files can be hierarchical and encrypted for security.

✅ ASP.NET Data Binding

🔷 What is Data Binding?

Data binding in ASP.NET is the process of connecting UI controls (like GridView, DropDownList, etc.) to a data source such as:

A database
A collection (Array, List)
An object
XML files

Once bound, the control can display, update, or interact with that data automatically.

🔷 Types of Data Binding

Type	Description
Simple Data Binding	Binds a single value to a control (e.g., TextBox.Text = value)
Complex Data Binding	Binds a list or table of data to controls like GridView or DropDownList
Two-way Binding	Allows data to flow both from source to UI and UI to source (e.g., FormView)

🔷 Commonly Used Data-bound Controls

Control	Purpose
`GridView`	Displays data in a tabular format
`Repeater`	Displays repeated list of items with custom layout
`DataList`	Displays items in any layout (like table or cards)
`DropDownList`	Displays a list of selectable items
`FormView` / `DetailsView`	Display/edit a single record at a time

🔷 Common Data Sources

SqlDataSource
ObjectDataSource
XmlDataSource
EntityDataSource
LinqDataSource

🔷 Example: Binding Data to GridView

📄 ASPX Page

<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="true" />

📄 Code-behind (C#)

protected void Page_Load(object sender, EventArgs e)
{
    if (!IsPostBack)
    {
        List<string> names = new List<string> { "Alice", "Bob", "Charlie" };
        GridView1.DataSource = names;
        GridView1.DataBind();
    }
}

🔷 Using `SqlDataSource` for Binding

<asp:SqlDataSource ID="SqlDataSource1" runat="server"
    ConnectionString="<%$ ConnectionStrings:MyDB %>"
    SelectCommand="SELECT * FROM Students">
</asp:SqlDataSource>

<asp:GridView ID="GridView1" runat="server" 
    DataSourceID="SqlDataSource1" 
    AutoGenerateColumns="true">
</asp:GridView>

⚙ No code-behind needed. The data is fetched automatically.

🔷 Key Methods

Method	Description
`DataBind()`	Binds the data source to the control
`IsPostBack`	Ensures data is not bound again on every postback

🔷 Advantages of Data Binding

✅ Separates logic from UI ✅ Reduces manual code ✅ Easy to connect to databases ✅ Supports sorting, paging, editing (in some controls like GridView)

🔷 Two-Way Data Binding Example

<asp:TextBox ID="TextBox1" runat="server" Text='<%# Bind("Name") %>' />

✅ Summary

ASP.NET Data Binding connects UI controls to data sources.
Can be simple (TextBox) or complex (GridView).
Uses DataBind() or declarative data sources like SqlDataSource.
Provides a quick and consistent way to display, update, and manage data.

Website navigation refers to how users move between different pages of a web application. In ASP.NET, navigation is structured using special controls and configuration files that help define the site's structure, menu, and page hierarchy.

Navigation Type	Description
Hyperlinks	Use `<a>` tags or `HyperLink` controls to link pages
Server.Transfer / Response.Redirect	Navigate programmatically between pages
Navigation Controls	Use `Menu`, `TreeView`, `SiteMapPath`, etc.
Site Map	Central XML file (`Web.sitemap`) that defines the website’s structure

1. 🧭 `Menu` Control

Displays a menu bar (horizontal or vertical) with items and sub-items.

<asp:Menu ID="Menu1" runat="server" DataSourceID="SiteMapDataSource1" Orientation="Horizontal" />

2. 🌲 `TreeView` Control

Displays navigation in a tree structure (like folders and subfolders).

<asp:TreeView ID="TreeView1" runat="server" DataSourceID="SiteMapDataSource1" />

3. 🧶 `SiteMapPath` Control (Breadcrumbs)

Displays the navigation path (e.g., Home > Products > Laptops).

<asp:SiteMapPath ID="SiteMapPath1" runat="server" />

🔷 Web.sitemap File (Site Map)

This is an XML file that defines the website’s navigation structure.

🗂 Sample Structure:

<siteMap xmlns="http://schemas.microsoft.com/AspNet/SiteMap-File-1.0">
  <siteMapNode title="Home" url="Default.aspx">
    <siteMapNode title="About Us" url="About.aspx" />
    <siteMapNode title="Products" url="Products.aspx">
      <siteMapNode title="Laptops" url="Laptops.aspx" />
      <siteMapNode title="Mobiles" url="Mobiles.aspx" />
    </siteMapNode>
  </siteMapNode>
</siteMap>

🔷 SiteMapDataSource

Connects navigation controls to the Web.sitemap file.

<asp:SiteMapDataSource ID="SiteMapDataSource1" runat="server" />

Method	Description
`Response.Redirect("Page.aspx")`	Redirects to a new page, starts a new request
`Server.Transfer("Page.aspx")`	Transfers to another page on the server, maintains context

✅ Centralized site structure via Web.sitemap ✅ Easy to update navigation items ✅ Built-in SEO-friendly menus ✅ Supports dynamic page trees ✅ Can integrate with role-based security

✅ Summary

ASP.NET provides rich navigation using controls and site map files.
Key controls: Menu, TreeView, SiteMapPath.
The Web.sitemap file defines the entire site structure.
Navigation can be done via controls or programmatic redirection.

✅ Personalization in ASP.NET

🔷 What is Personalization?

Personalization in ASP.NET refers to the process of customizing the content, appearance, and behavior of a web application based on individual user preferences.

It helps create a user-centric experience by remembering settings like:

Layout choices
Theme selection
Favorite pages or items
Recently viewed content
Dashboard configuration

🔷 Why Use Personalization?

Benefit	Explanation
🎯 User Focus	Delivers content tailored to each user
💾 Saves Preferences	Remembers user settings between visits
🧩 Enhances UX	Offers a more interactive and adaptive interface
🔒 Secure	Can store preferences securely on a per-user basis

🔷 Personalization Features in ASP.NET

ASP.NET supports personalization primarily through:

Web Parts Personalization
Profile Properties (in web.config)
Cookies or Session-based Preferences

🔷 1. Web Parts Personalization

Web Parts allow users to customize the layout and content of a web page dynamically, e.g., moving panels, hiding widgets.

Components:

Component	Description
`WebPartManager`	Manages all Web Part behavior
`WebPartZone`	Container for Web Part controls
`CatalogZone`	Allows adding new parts
`EditorZone`	Allows editing title, layout, etc.

Example:

<asp:WebPartManager ID="WebPartManager1" runat="server" />
<asp:WebPartZone ID="WebPartZone1" runat="server">
    <ZoneTemplate>
        <asp:Calendar ID="Calendar1" runat="server" />
    </ZoneTemplate>
</asp:WebPartZone>

🔐 Personalization settings are stored in the ASP.NET SQL personalization database.

🔷 2. Profile Properties (User-Based)

ASP.NET allows you to define user-specific properties in web.config using <profile> section.

Example in `web.config`:

<configuration>
  <system.web>
    <profile>
      <properties>
        <add name="Theme" type="string" defaultValue="Light" />
        <add name="FontSize" type="int" defaultValue="12" />
      </properties>
    </profile>
  </system.web>
</configuration>

Access in Code (C#):

string theme = Profile.Theme;
int fontSize = Profile.FontSize;

✅ Works only for authenticated users (unless anonymous personalization is enabled).

🔷 3. Session/Cookie Based Personalization

If profile features are not enabled, you can use Session or Cookies to store and retrieve user preferences.

Session["Theme"] = "Dark";

string theme = (string)Session["Theme"];

🔐 Security Note

Always validate user input before storing it.
Profiles and personalization data can be stored in the SQL Server ASP.NET membership database.

✅ Summary

Feature	Description
Web Parts	Drag/drop panels, user-customizable layouts
Profile Properties	Stores preferences like theme, font size per user
Session/Cookies	Lightweight, custom way to remember user choices

📌 Key Points for Exams

ASP.NET supports personalization using Web Parts and Profile Properties.
Personalization improves user experience.
Web Parts are great for dashboard-style applications.
Profiles are defined in web.config and accessed through Profile object.

ASP.NET Advanced Features

✅ Web Parts in ASP.NET

🔷 What are Web Parts?

🔷 Key Features

🔷 Components of Web Parts

🔷 Modes of WebPartManager

🔷 Example: Simple Web Part Page

📄 ASPX Page

📄 Code-Behind (C#)

🔷 Personalization

🔷 Advantages

🔷 Real-Life Use Cases

✅ Summary

✅ ASP.NET Configuration

🔷 What is ASP.NET Configuration?

🔷 Main Configuration Files

🔷 Structure of web.config

🔷 Important Configuration Sections

🔹 1. <appSettings>

🔹 2. <connectionStrings>

🔹 3. <system.web>

🔹 4. <customErrors>

🔹 5. <trace> and <compilation>

🔷 Multiple web.config Files

🔷 How to Edit Configuration

🔷 Security Tip

✅ Summary

✅ ASP.NET Data Binding

🔷 What is Data Binding?

🔷 Types of Data Binding

🔷 Commonly Used Data-bound Controls

🔷 Common Data Sources

🔷 Example: Binding Data to GridView

📄 ASPX Page

📄 Code-behind (C#)

🔷 Using SqlDataSource for Binding

🔷 Key Methods

🔷 Advantages of Data Binding

🔷 Two-Way Data Binding Example

✅ Summary

✅ Website Navigation in ASP.NET

🔷 What is Website Navigation?

🔷 Common Navigation Methods in ASP.NET

🔷 Website Navigation Controls

1. 🧭 Menu Control

2. 🌲 TreeView Control

3. 🧶 SiteMapPath Control (Breadcrumbs)

🔷 Web.sitemap File (Site Map)

🗂 Sample Structure:

🔷 SiteMapDataSource

🔷 Programmatic Navigation (C#)

🔷 Advantages of ASP.NET Navigation System

✅ Summary

✅ Personalization in ASP.NET

🔷 What is Personalization?

🔷 Why Use Personalization?

🔷 Personalization Features in ASP.NET

🔷 1. Web Parts Personalization

Components:

Example:

🔷 2. Profile Properties (User-Based)

Example in web.config:

Access in Code (C#):

🔷 3. Session/Cookie Based Personalization

🔐 Security Note

✅ Summary

📌 Key Points for Exams

🔷 Structure of `web.config`

🔹 1. `<appSettings>`

🔹 2. `<connectionStrings>`

🔹 3. `<system.web>`

🔹 4. `<customErrors>`

🔹 5. `<trace>` and `<compilation>`

🔷 Multiple `web.config` Files

🔷 Using `SqlDataSource` for Binding

1. 🧭 `Menu` Control

2. 🌲 `TreeView` Control

3. 🧶 `SiteMapPath` Control (Breadcrumbs)

Example in `web.config`: