Miguel's place

Stumbled across a good debugging post

2006-04-21T04:47:00Z

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 ;)

New Transactions forum

2006-03-14T09:37:00Z

Out from my blog coma I come. The Transactions team now has a dedicated forum that can be accessed here. Shoot us some questions!

More on Transactional Notepad

2005-09-09T18:11:00Z

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!!!

Regarding Poorly-Named Dialog Buttons

2005-09-09T05:54:00Z

In one of Adam Nathan's recent posts he gripes about one of his pet peeves, which is that the cancel button in dialogs usually doesn't undo any work that has been done through the dialog when you click cancel. It just closes the dialog.

I agree and am looking forward to seeing this change when people see how easy we (the Transactions team) are making the use of Transactions starting with System.Transactions in Whidbey. Granted it is still a ways in the future, but it's on it's way I tell you!

With Whidbey you would be able to write a transaction aware managed text editor that had a transacted replace dialog that really would undo all the changes on cancel! The cost of entry to developing a resource manager has dropped considerably with Whidbey and makes things like this not only simpler but more likely in the future. Not to mention that since the resource manager that managed the text would be a volatile resource manager (and most likely the only resource manager to be enlisted on the Transactions) it would be very performant given our pay for play model in System.Transaction.

Additionally, when txF becomes available, the "undoing" of file name changes, deletes, moves, creations, etc.. from a file chooser dialogue could be undone if done from within a transaction!

Hello World!

2005-08-02T20:21:00Z

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".