Hi!

In the book, it was mentioned that TransactionScope shouldn't be used in a shared web hosting environment because the server could be reconfigured... Could someone clarify that for me? I'm building a CMS to be hosted on a shared server, but I would really like to use TransactionScope in the BLL.

Thx,

C.

P.S. Great book! I'm hoping you guys do another Problem - Design - Solution book for Windows Form development!

You obviously can't control the transaction scope outside of your web application. The problem would be any attempt to enlist in a wider scope than you are allowed to use. This happens automatically in some cases.

If you can contain the scope to your app only, it "might work". That's the best assurance you can get when it comes to MTS on a shared server.

There won't be a Winforms book like this because Windows apps are highly specialized by their nature. It's hard to find a need for a general purpose application for Win Forms. Besides, all the Windows fat client book focus is already moving to WPF. You should check into WPF!

Silverlight is the new compelling web technology after AJAX. I wish the world would slow down so I can keep up with all this stuff!

Eric

Thanks for the response, but I'm still rather unclear:

>You obviously can't control the transaction scope outside of your
>web application. The problem would be any attempt to enlist in a
>wider scope than you are allowed to use. This happens automatically
>in some cases.

I don't understand what you mean about the transaction scope being outside of my application. If I look at the BLL of the TBH (Order object), I had thought the scope began and ended in the BLL, with a trickling down to the DAL so that commands could be properly transactioned. Could we not specify the transaction scope as root? Would that prevent an attempt to enlist in an ambient scope I don't have access to?

Do all databases work with TransactionScope? I'm really jazzed about the concept, it would make my code much more elegant.

Cheers,

C.

The whole idea behind MTS is to allow different tiers and different applications to participate in the same transaction. For example, if you call a COM object hosted as COM+, then it can participate in the same transaction. This can either be automatic (auto-enlistment) or manual. Manual is good in my book because it lets me decide the span of the transaction. Auto enlistment is easy, but dangerous.

Oracle can support MTS transactions, but that support may require an extra software layer that has an extra fee. I don't know about other DBMS's.

Web Services also can't participate in MTS transactions yet. Even the super-cool WCF can only support single call transactions at this time. Full transaction support in services will arrive someday, but not soon.

Eric