Skip to main content

Cross Page Posting and Exceptions in ASP.NET Page



HTMLForm.SubmitDisabledControls = true; will disable the controls while the page is being submitted.

One Server Side Visible HTMLForm is supported in a Web Page. Other Form <form> tags should client side only with action=”search.aspx” and method=”post” attributes. And for the fact one will have to use old fashioned code to retrieve values:

string textToSearch = Request.Form["Keyword"].ToString();

In CrossPagePostback Specify the PostbackURL for <asp:Button> in which following script will be written to postback to a different page:

In this case a new hidden field will be generated __PREVIOUSPAGE to provide viewstate information of previous page.

CrossPagePosting is a two way process in which Source page first postsback to itself then to the Target page specified in PostabkURL.

Detecting CrossPagePostback:
          if (PreviousPage == null)
{
          if (!PreviousPage.IsCrossPagePostBack)
{
Response.Write("Sorry, that's the wrong way to invoke me.");
Response.End();
return;
                   }
}
If PreviousPage contains validators then use:

if (!PreviousPage.IsCrossPagePostBack)
{
}

In case of Server.Transfer to obtain previous page in ASP.NET 1.x use:
            Page caller = (Page) Context.Handler;

But in ASP.NET 2.0 &+ PreviousPage can be used and <@% PreviousPageType %> can used for strongly type access. But in case of Server.Transfer IsCrossPagePostBack is set to false.

Exception Handling:
Showing a custom page for all exception and showing a specific page on a specific error code:

<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="/GenericError.aspx">
<error statusCode="404" redirect="/ErrorPages/Error404.aspx" />
<error statusCode="500" redirect="/ErrorPages/Error500.aspx" />
</customErrors>
</system.web>
</configuration>

Path to the page is passed through the Query string to exception handling page that can be retrieved as:
                   Request.QueryString["AspxErrorPath"];
To Write Trace information to other listeners that are registered in <System.Diagnostics> Sections.

Personalization:
          ProfileModule is responsible for loading information from the Storage Medium and making them available.

To load a different profile, handle the Profile_Personalize method in global.asax.

void Profile_Personalize(object sender, ProfileEventArgs e)
{
          ProfileCommon profile = null;
profile = (ProfileCommon) ProfileBase.Create("Guest");

// Make the HTTP profile module use THIS profile object
if (profile != null)
e.Profile = profile;
}


Writing Custom Profile Provider:
         http://msdn.microsoft.com/msdnmag/issues/07/03/ASPNET2/default.aspx

One can use a different provider for each property as shown:

          <properties>
                   <add name="BackColor" type="string" provider="MyProvider" />
                   <add name="TabSettings" type="string" provider="SqlProvider" />
</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...

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