I know using NH with ambient transactions has been discussed previously, but I have a slightly different scenario. I am using Rhino Service Bus which creates a TransactionScope. During a message handler, I am 1. doing some ADO.net work directly on one database 2. using NH to do some other work on another database. (only one session factory in use)
I am getting the warning in the subject of this post but when I skip the manual ado.net work I do not. Have others experienced similar issues when mixing straight ado.net work with nh using TransactionScope? I am not quite sure where to hunt down what I am doing wrong though I am sure it is related to the connection on my own code. Forgive me for not posting code but I wasn't sure it would be useful in this situation. mike
-- 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.
