S
Shawn B.
Greetings,
I have a object that gets created and interted into the Application object
of my ASP.NET application, that internally contains a Timer that elepses
every so often (once a minute by default).
In the event that it raises, I must access the Application object and work
with some things that are stored in it.
The problem is that the Application object is always null when this
happens... e.g. System..Web.HttpContext.Current.Application always returns
null.
My guess is that it only has a current context during a page request and
since this isn't happening inside a page request, it is null.
My question is, how can I access this Application object? It is global so
it should be there, unlike the Session and so on.
Before I get answers about the usual (make it a service) you must understand
that this is not an option for me, the project is on a hosted server and I
don't have the ability to deploy a service (unless I pay unfathomaly amounts
of money to have them review the code, test it, and whatever else before
they'll deploy it).
Thanks,
Shawn
I have a object that gets created and interted into the Application object
of my ASP.NET application, that internally contains a Timer that elepses
every so often (once a minute by default).
In the event that it raises, I must access the Application object and work
with some things that are stored in it.
The problem is that the Application object is always null when this
happens... e.g. System..Web.HttpContext.Current.Application always returns
null.
My guess is that it only has a current context during a page request and
since this isn't happening inside a page request, it is null.
My question is, how can I access this Application object? It is global so
it should be there, unlike the Session and so on.
Before I get answers about the usual (make it a service) you must understand
that this is not an option for me, the project is on a hosted server and I
don't have the ability to deploy a service (unless I pay unfathomaly amounts
of money to have them review the code, test it, and whatever else before
they'll deploy it).
Thanks,
Shawn