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

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...