Linq context object. Right now the latest fix I have done is to lock
the context object while doing any db operation.
Seems to work for now...
I will post if there are further issues and find any new fix.
I have to use linq as it is faster for development and so far, though
it has been a pain to understand and learn, I think I am finally
getting a taste of how effectively to use it.
I want to use it for it's caching abilities which is why I like to
share a context object across threads. It is a shame that only one
operation can be done by it at any point of time..
No comments:
Post a Comment