Diego, Doesn't that completely fly in the face of what TransactionScope is supposed to do? The whole point of transactionscope is exactly that you don't need to explicitly manage transactions.
If you check the thread I refer to in my original mail you'll see that Ayende considered that behavior a bug that could be worked around by using explicit transactions (http://www.mail-archive.com/rhino-tools- [email protected]/msg02447.html). I don't see how having to use explicit transactions is a good thing. If there's any point in continuing this then I'd be more than happy to continue on nhusers. On Nov 4, 3:52 pm, Diego Mijelshon <[email protected]> wrote: > NHibernate will automatically enlist its transactions in the > transactionscope, BUT you still have to open them. > (BTW, this group is for the development of NH; use nhusers for usage > questions) > > Diego > > On Thu, Nov 4, 2010 at 11:24, Eldritch Palmer > <[email protected]>wrote: > > > > > > > > > Oskar, > > > I'm currently not explicitly opening any NH transactions. > > As far as I can tell NHibernate should automatically enlist in the > > transaction created by the transactionscope. > > If this is not the case then that would be a pain (that is what I was > > referring to in my initial post) > > > Can you reproduce the issue? > > > Eldritch > > > On Nov 4, 2:57 pm, Oskar Berggren <[email protected]> wrote: > > > Where are you opening you NHibernate transactions? > > > > /Oskar
