I have made a background thread running once a day that is responsible for doing some work on PurchaseOrders in the database - ie. it is changing order statuses and adding audit trails.
The method I have to do the job throws an exception when running in the background. The error says that HttpContext.Current is null (of course).
HttpContext.Current is null. PerWebRequestLifestyle can only be used in ASP.Net
By default the components configured in uCommerce assume a web context, but you can change that to match your environment by editing the components.config file placed with your console app.
You want to change the lifestyle of a couple of data access components to "Thread" instead of "PerWebRequest".
Is there a way to make the change dynamically at runtime? The thing is, I need to do some maintenance work on the database and I would like to have that done in a System.Timers.Timer and not have it done with a page request - since I don't want users to experience slow load times because I have some maintenance to do.
But you could instantiate the session provider yourself and use that:
using System.Linq; using NHibernate; using NHibernate.Linq;
var sessionProvider = new SessionProvider(); using (var session = sessionProvider.GetSession()) { //Select() is like All() session.Query<Product>().Select(); }
From here you can do all the queries you're used to just with a different starting point.
Doing database work in a background thread
Hello,
I have made a background thread running once a day that is responsible for doing some work on PurchaseOrders in the database - ie. it is changing order statuses and adding audit trails.
The method I have to do the job throws an exception when running in the background. The error says that HttpContext.Current is null (of course).
I'm using
to query the entries in the table.
Why is this depending on the HttpContext, and can I get around it somehow?
By default the components configured in uCommerce assume a web context, but you can change that to match your environment by editing the components.config file placed with your console app.
You want to change the lifestyle of a couple of data access components to "Thread" instead of "PerWebRequest".
The services in question are:
Thanks Søren (and sorry for my late reply).
Is there a way to make the change dynamically at runtime? The thing is, I need to do some maintenance work on the database and I would like to have that done in a System.Timers.Timer and not have it done with a page request - since I don't want users to experience slow load times because I have some maintenance to do.
There's not.
But you could instantiate the session provider yourself and use that:
From here you can do all the queries you're used to just with a different starting point.
is working on a reply...