Okay, I have been trying to peice this together - and I know folks on this
board have the answer.
What is the common ground between System.Transactions and SqlTransaction?
Would it be correct to say that -
For most of my work that interacts with one single database, as far as I can
see so far, I should stick with the old fashioned SqlTransaction.
And well if I need or might have to deal with the possibility that I would
have to ever promote my transaction to more than one database, or to other
non d/b like resources like MSMQ, then System.Transactions is what I need.
In that sense it is incorrect to think that -
SqlTransaction is a baby System.Transactions.Transaction.Create()
SqlTransaction is going to be deprecated anyday soon.
System.Transactions.Transaction is the way to go - and SqlTransaction is
not.
Either SqlTransaction or System.Transactions is dud - they both kick a33,
but serve different purposes.
SqlTransaction is an orange, System.Transaction is an apple - both are
fruits but can't be compared.
Again - my understanding about this could be totally out of whack - and I am
hoping someone will fix my understanding of the matter.
I've also blogged about this here -
http://dotnetjunkies.com/WebLog/sahilmalik/archive/2004/12/06/35314.aspx
(and other posts).
All in all I am very excited about System.Transactions but I don't want to
misuse it :-)
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik