Skip to main content

Master Pages in ASP.NET



Master Pages:

Master Page inherits from UserControls.

<asp:Content> element corresponds to Content class.

          If Content Page doesn’t define a content against a <asp:ContentPlaceholder> of master Page then default contents of the <asp:ContentPlaceholder> defined in it’s opening and closing tags are used to fill the gap.


Browser Specific Master Pages:
          <%@  Page masterpagefile="Base.master"
ie:masterpagefile="ieBase.master"
netscape6to9:masterpagefile="nsBase.master" %>

ID of Most Common Browsers
Browser ID               Browser Name
IE                          Any version of Internet Explorer
Netscape3               Netscape Navigator 3.x
Netscape4               Netscape Communicator 4.x
Netscape6to9           Any version of Netscape higher than 6.0
Mozilla                    Firefox
Opera                     Opera
Up                         Openwave-powered devices

In ASP.NET 1.x, you find it in the <browserCaps> section of the machine.config file. In newer versions a .browser file in Framework\[version]\Config\Browsers.

To set title in Content Page use Title attribute of <%@ Page>:
<@Page MasterPageFile="simple.master" Title="Hello, master" %>

Accessing Master Page Properties, Variables, and methods:

   <%@ Master Inherits="SimpleWithProp" Classname="MasterWithProp" %>
   ((ASP.MasterWithProp)Master).TitleBoxText = "Programming ASP.NET 3.5";

Or By Specifying MasterPageType:

CSS VS Themes:
Themes are better as providing facility to predefine controls properties as well.

When themes are applied settings are not overrideable in .aspx but can be overrided in Init and Load event.

To disable Theming on a control use EnableTheming Boolean property.

Page allows to reset EnableTheming only in Page_PreInit event.

Themes Css Files are linked to the head element of the target Page.

To disable Theming on custom or web controls or for it’s properties use the property:

[Themeable(false)]

Getting Themes available in application:
protected StringCollection GetAvailableThemes()
{
string path = Request.PhysicalApplicationPath + @"App_Themes";
DirectoryInfo dir = new DirectoryInfo(path);
StringCollection themes = new StringCollection();
foreach (DirectoryInfo di in dir.GetDirectories())
themes.Add(di.Name);
return themes;
}

Working With Wizard Control:
          Major Supported Templates Include:
FinishNavigationTemplate (Previous and Finish Button Template)
HeaderTemplate
SideBarTemplate
StartNavigationTemplate
StepNavigationTemplate
Major Properties of the Wizard Control include:
ActiveStep
ActiveStepIndex
DisplayCancelButton
DisplaySideBar
HeaderText
SkipLinkText
WizardSteps

public ICollection GetHistory() will return WizardStepBase collection in History order of the user’s access. Current step is at 0 location.

Major Events Supported are:
ActiveViewChanged
CancelButtonClick
FinishButtonClick
NextButtonClick
PreviousButtonClick
SideBarButtonClick

AllowReturn Property of WizardStep (default:true) to false will disable use from returning to this step.

SideBarTemplate(if user defined) must contain a DataList having ID = “SideBarList” and <ItemTemplate> must contain a Button (IButtonControl) control with name(ID = “SideBarButton”).

Delegate used for Events:
public delegate void WizardNavigationEventHandler(object sender, WizardNavigationEventArgs e);

If (WizardNavigationEventArgs e) e.Cancel is set to true then navigation to next, previous or any step is blocked and current step remains visible. This may be because of any invalid data entered.

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

ASP.NET Working with Web Configuration Files

Our sites are configured based on hierarchy of XML configuration files. Machine.config is top level configuration file located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\machine.config These settings are framework level and common to all Windows, Console, Class Library, and Web application. Some of them could be overridden in Web.config while others are protected. Next in hierarchy is Root.config. It’s located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\web.config It contains default web server settings. Optionally one can add at root of all websites a web.config to provide general settings related to all sites. Optionally to provide more control on settings one can add web.config in each web site and for each folder in that web site. Processing the Configuration files:                       ...