TransactionScope and Concurrency?

With the typical example of implementing calls that leverage
TransactionScope (via a using code block) - would this be "safe" for
asp.net web apps? I am finding some conflicting opinions on the net
about this issue.

Because transaction enlisting is inherent by all calls in the code
that executes (within the using block), would User A's rollback cause
User B's to rollback too if they both hit at the same time?

On Apr 30, 10:15*am, znelson <znel...@gmail.com> wrote:
> With the typical example of implementing calls that leverage
> TransactionScope (via a using code block) - would this be "safe" for
> asp.net web apps? I am finding some conflicting opinions on the net
> about this issue.
>
> Because transaction enlisting is inherent by all calls in the code
> that executes (within the using block), would User A's rollback cause
> User B's to rollback too if they both hit at the same time?

I answered my own question with a little testing - each user's
transaction is unique and one does not affect the other.