Expert |
|
Joined: Fri May 13, 2005 5:56 pm Posts: 308 Location: Santa Barbara, California, USA
|
in an ASP.NET app, i can say from my own experience that this type of error generally happens when you are trying to load a lazy collection in an object that was opened in a past session. there is so much more to the problem, though, so i'm assuming alot. if you think you are running into such a scenario, then you need to look at the session.Lock() method as one of probably three or four ways to fix this error.
-devon
|
|