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.
Labels:

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...
Post a Comment
Continue Reading »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...
Post a Comment
Continue Reading »