Question

This is possibly very lame question and I lack knowledge about ASP.Net. In this case a link to an article explaining would be very welcome.

I’m working on web-site on ASP.NET with C# as codebehind. My current project involves developing few pages with very similar functionality and a many functions are the same. For example

private void PermissionCheck()
{
    if (null == Session["UserID"] ||
        null == Session["ProjectID"] ||
        null == Session["AssetID"] ||
        null == Session["ProjectName"])
    {
        Response.Redirect("~/Login.aspx");
    }
 }

Would be the same on 2 pages. Some other things are the same as well. I would like to put this into common base class. But there are other functions that don’t really belong to pages at all:

private string GetAttachmentTempPath()
{
    return Request.PhysicalApplicationPath + WebConfigurationManager.AppSettings.Get("AttachmentsTempFolder");
}

I would like to move this into Attachment class, but to get the physical path of the application, I need to pass in Request object into that method, which is not really nice, as it couples Attachment class with Page.Request object.

Is there any way to move these functions somewhere else without needing to pass Page.Request objects around??

p.s. The appliction is huge, and there is no scope to change the entire architecture.

Answer 1

For your permission thing you could make a base page class:

class BasePage : Page
{ 
   ...
   protected override OnInit() {
     // do check here
   }
}

Now you can implement your page like this class MyOtherPage : BasePage { ... }
The OnInit gets executed everytime your MyOtherPage gets loaded.

You can see a complete page lifecycle here: Link

For your other problem: Consider to implement a global available static tool class

Update

A good approach for making things like web.config easier to access is a Singleton. In asp.net a singleton is only created once and lives until the asp worker process gets stopped . So this values are shared across the whole asp.net application. This is also good for storing data in a global context that you dont want to get out of your database or file anytime a user makes a page request (for example a version number or things like that)

Update 2

To access the request without passing it to every function, use this:

HttpContext.Current.Request