I love the new System.Transaction found in .NET 2.0. I have been and will continue to use it in my applications.
When you compare it with for example the Enterprise Service management it’s so slim and lightweight. And the scaling up to SQL 2005 Transactions when need is a feature that will be nice when that kick in.
My favorite among them all, though, is the TransactionScope, which makes a nice and easy visual way of showing what is part of the transaction and not.
However, i found out a small glitch yesterday. Appearently there is a configuration value (maxTimeout) hidden away in the machine.config-file on each computer. This value defaults to ten minutes and that value overrides any values found in other configs (web.config or app.config).
So - if you need long running transaction you will have to tweak that value. See this articles for more information.
- http://blogs.msdn.com/madhuponduru/archive/2005/12/16/504730.aspx
- http://msdn2.microsoft.com/en-us/library/system.transactions.configuration.defaultsettingssection.aspx
- http://msdn2.microsoft.com/en-us/library/system.transactions.configuration.machinesettingssection.aspx
But … i still love it!