correct you do not want you entities to cross sessions. you can but it requires you to detach from session 1 and attach to session 2. I would consider the need for this to be an edge case.
On Nov 19, 11:30 pm, "Scott W." <[email protected]> wrote: > I definitely think this is caused by me managing my session and > transactions incorrectly. Here is a great article by Ayende that > clears up a lot of info for > me:http://msdn.microsoft.com/en-us/magazine/ee819139.aspx > > I think if I want to take an entity that was loaded in one session and > save it in another session, I have to manually copy the data from the > detached entity to one I've loaded from the database in the new > session. As the article states, I would be better off structuring my > application so I have one session per form and one transaction per > user action, rather than one session and transaction per user action > like I have now. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
