Skip to main content

ASP.NET Site Navigation Techniques



Some times we navigate to multiple pages in-order to gather particular information. We can use Wizard and FormView controls in that scenarios.

Choosing a method for navigation:

Client Side Markup to request new page: Using client side button link.
Cross-Page posting: Control configured to postback to a different page.
Issue Client-side browser redirect: Server sends a message to browser to request a different page.
Issue Server-side transfer: Transfers control to a different page.

1. Providing Client Side Markup to Request new page:
Use <asp:HyperLink> control and provide NavigationUrl. It renders to <a> tag.
User <input type=”button” onclick=”return MoveToNextPage()”> provide onclick javascript event.

<JavaScript> function MoveToNextPage() { document.location = “AddUser.apsx”; } </JavaScript>

2. Cross-Page Posting:

Button can be give “PostBackUrl” to postback to.
To get control from previous page call PreviousPage.FindControl(“txtFirstName”) as it’s a naming container.

Accessing Strongly Typed Data:
Button can be give “PostBackUrl” to postback to.
In source page add a pubic property to return data.
public string UserName { get { return txtFirstName.Text; } }

In target page tell him the Page type
à
<%@PreviousPageType VirtualPath = “~/AddUser.aspx” %>
In target page check “PreviousPage” if not null Cross-Page posting occurs.

Then to get data call PreviousPage.UserName.


3. Issuing Client side Browser Redirect:
Call Response.Redirect which sends 302 code with a url to client browser request this URL Page.
Prior to executing Reponse.Redirect
Set Response.BufferOutput = true;
This causes Browser not to send any data to client prior to executing Redirect.

If response headers are sent and than redirect command is issued an HTTP exception will raise.

PreviousPage will not be accessible.

4. Issuing Server-Side Transfer:
HttpUtility.Transfer is used. Page contains a Sever property that gives you access to Transfer as well (Server.Transfer).
PreviousPage property is available.
Server.Transfer(“AddUser.aspx”, false /*preserveForm*/);
Pass true value as preserveForm parameter to preserver QueryString and form data.

Using the SiteMap Web Server control:
Used to define and display Site’s structure.

Following controls can display site map data.
Menu, TreeView and SiteMapPath.
SiteMapPath: Displays CurrentNode and the path to current Node like a breadcrumb control. HOME > Visual Studio > Support
These controls generate markups and server side events as well,
TreeView and Menu require SiteMapDataSource control.
By Default SiteMapDataSource picks its data from Web.sitemap; but SiteMapPath control gets data directly from Web.Sitemap.

Sample Web.Sitemap.






Using SiteMap class:

SiteMap to display site hierarchy. Properties include CurrentNode and RootNode that return SiteMapNode. SiteMapNode have the properties like Title, URL, and Description. To access other node SiteMapNode provides ParentNode, ChildeNodes, NextSibling, and PreviousSibling properties.

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

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

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