You don't have to. Using the default flushing behaviour, TransactionScopes don't flush unless they are committed and disposed.
-Markus 2009/8/13 vitalya <[email protected]> > > Hello Everyone, > > I've got a question, how do I create a TransactionScope with > FlushAction.Never? the problem is, that there is no overloaded > constructor, and currently the only option available, is to use > configuration, as far as TransactionScope constructor defines a > default value FlushAction.Config. > Is there a reason, to create a patch with overloaded constructor? > > Thanks in advance > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
