Why is HttpContext.Current null?


I have a value that I use in all the application; I set this in application_start

  void Application_Start(object sender, EventArgs e)
    Dictionary<int, IList<string>> Panels = new Dictionary<int, IList<string>>();
    List<clsPanelSetting> setting = clsPanelSettingFactory.GetAll();
    foreach (clsPanelSetting panel in setting)
        Panels.Add(panel.AdminId, new List<string>() { panel.Phone,panel.UserName,panel.Password});
    Application["Setting"] = Panels;

    SmsSchedule we = new SmsSchedule();


and in SmsSchedule

public class SmsSchedule : ISchedule
    public void Run()
        DateTimeOffset startTime = DateBuilder.FutureDate(2, IntervalUnit.Second);
        IJobDetail job = JobBuilder.Create<SmsJob>()

        ITrigger trigger = TriggerBuilder.Create()
             .WithSimpleSchedule(x => x.WithIntervalInSeconds(60).RepeatForever())

        ISchedulerFactory sf = new StdSchedulerFactory();
        IScheduler sc = sf.GetScheduler();
        sc.ScheduleJob(job, trigger);


I want to get this value in a class.(smsjob)

   public class SmsJob : IJob 
      public virtual void Execute(IJobExecutionContext context)

but my problem is : HttpContext.Current is null, why is HttpContext.Current null?

Edit: When i use this code in another class of a page it works, but in this class I get the error.

This question is tagged with c# asp.net iis httpcontext

~ Asked on 2013-10-22 05:31:09

The Best Answer is


Clearly HttpContext.Current is not null only if you access it in a thread that handles incoming requests. That's why it works "when i use this code in another class of a page".

It won't work in the scheduling related class because relevant code is not executed on a valid thread, but a background thread, which has no HTTP context associated with.

Overall, don't use Application["Setting"] to store global stuffs, as they are not global as you discovered.

If you need to pass certain information down to business logic layer, pass as arguments to the related methods. Don't let your business logic layer access things like HttpContext or Application["Settings"], as that violates the principles of isolation and decoupling.

Update: Due to the introduction of async/await it is more often that such issues happen, so you might consider the following tip,

In general, you should only call HttpContext.Current in only a few scenarios (within an HTTP module for example). In all other cases, you should use

instead of HttpContext.Current.

~ Answered on 2013-10-22 07:29:52


In IIS7 with integrated mode, Current is not available in Application_Start. There is a similar thread here.

~ Answered on 2013-10-22 05:40:47

Most Viewed Questions: