Why is HttpContext Current null

Question

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 lt int  IList lt string gt  gt  Panels   new Dictionary lt int  IList lt string gt  gt         List lt clsPanelSetting gt  setting   clsPanelSettingFactory GetAll        foreach  clsPanelSetting panel in setting                Panels Add panel AdminId  new List lt string gt      panel Phone panel UserName panel Password              Application  Setting     Panels       SmsSchedule we   new SmsSchedule        we Run           and in SmsSchedule   public class SmsSchedule   ISchedule       public void Run                            DateTimeOffset startTime   DateBuilder FutureDate 2  IntervalUnit Second           IJobDetail job   JobBuilder Create lt SmsJob gt                 WithIdentity  job1                Build             ITrigger trigger   TriggerBuilder Create                 WithIdentity  trigger1                 StartAt startTime                WithSimpleSchedule x   gt  x WithIntervalInSeconds 60  RepeatForever                  Build             ISchedulerFactory sf   new StdSchedulerFactory            IScheduler sc   sf GetScheduler            sc ScheduleJob job  trigger            sc Start              I want to get this value in a class  smsjob      public class SmsJob   IJob               public virtual void Execute IJobExecutionContext context                    HttpContext Current Application  Setting                    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

User · Answer

In IIS7 with integrated mode  Current is not available in Application Start  There is a similar thread here

User · Answer

try to implement Application AuthenticateRequest instead of Application Start   this method has an instance for HttpContext Current  unlike Application Start  which fires very soon in app lifecycle  soon enough to not hold a HttpContext Current object yet    hope that helps

User · Answer

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    Page Context https   docs microsoft com en-us dotnet api system web ui page context view netframework-4 7 2  Controller HttpContext https   docs microsoft com en-us dotnet api system web mvc controller httpcontext view aspnet-mvc-5 2   instead of HttpContext Current

[c#] Why is HttpContext.Current null?

Examples related to c#

Examples related to asp.net

Examples related to iis

Examples related to httpcontext