C#: Anything wrong with setting HttpContext.Current in a parallel thread?

I’m using a library that relies on HttpContext.Current. The library is Facebook C# SDK, but my question should apply in other scenarios as well. I’d like to use this library from inside of a parallel thread. However, HttpContext.Current is not available in the parallel thread, so I’m thinking about caching it to a local variable and then setting it in the parallel thread like this:

NHibernate Unable to convert MySQL date/time value to System.DateTime

I am getting the “Unable to convert MySQL date/time value to System.DateTime” error because from what I can tell I have a record with 0000-00-00 00:00:00. Now while the data should never be that (it should be null) there are cases when this might happen and I don’t want my entire application to crash because of it. I am using NHibernate and I tried adding change my connection string to allow zero datetime so the connection string configuration looks like: