Miguel's place

And figured that I can't seem to come up with any good content of my own I'll point some out.  Posts like this were what I set out with the intention of writing...

Note to Eran/CuttingEdge: You should take a look at the System.Transactions namespace.  More specifically, TransactionScope ;) 

Ok, so in taking a second longer to think about the problem, in reality the resource manager managing the text for the "Transaction aware Notepad" would need to be a durable resource manager.  However in the general case it would still be the only resource manager enlisted in the transactions.  This would still prevent escalation of the management of the transaction to msdtc and keep you on the fast track.  Although, if you were to do something like "Insert Image" (ok, so we're not talking about notepad any more) it would cause escalation of the transaction to msdtc if the open dialog was transaction aware and the image you selected was on a transactional file system. 

Hmm... using copy/paste potentially moves parts of the document beyond the process boundary.  Transactional clipboard that supports Promotable Single Phase Enlistment!!!

As if that that title hasn't been overdone to death for first blog posts... I promise, there will be more originality in time. 

So this will be yet another blog by a member of the Transactions team.  I am currently working on System.Transactions along with my fellow member of the Transactions cohort Nate.  I'll be diving into System.Transactions a bit, as well as debugging managed code from the windows debuggers since that's one of my favorite pasttimes :).

That's about it for this first post.  Wanted to keep it minimalist to "just get something out there".