ARGH!!! There seems to be a little confusion surrounding the SharedDbConnectionScope and TransactionScope objects to enable wrapping your SubSonic queries within a transaction. The docs suggest specifying the using SharedDbConnectionScope wrapped around the using TransactionScope... using(SharedDbConnectionScope scope = new SharedDbC...
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 ite...
I have not been able to get this working following the docs or other ideas people have tried. If i use the below, there is no transactional behaviour at all. If i swap the shareddbscope with the transaction scope around, i dont get a save on a single record. if it call ts.complete at the bottom of the transaction i get a single record s...
I'm looking at using Subsonic with a multi-tenant ASP.net web application. There are multiple DB's (one per client/instance). The user logs in with a domain suffix to their username (e.g. user@tenant1, user@tenant2). The custom membership provider will then determine which database a user is using, and authenticate against it. All user-...