views:

46

answers:

0

I have seen posts (first, second) on StackOverflow that say that SubSonic 2.2's SharedDbConnectionScope doesn't work with TransactionScope.

Can we still rely on SharedDbConnectionScope in other contexts? I want to know if I should be concerned when using code such as the following (where ProviderName is not the default provider for item's type):

using (var scope = new SharedDbConnectionScope(DataService.Providers[ProviderName]))
{
    item.Save();
}

In my system, it looks like it works fine, but I think I may have had it try to save to the wrong database on rare occasions (may be unrelated).

Thanks!