If your data access methods open multiple database connections in a Transaction scoped csla method, you’re going to get MSDTC errors (hopefully! since if you don’t you’re dev machine has too much good stuff on it and then you’re going to get the transaction controller errors later when you deploy.). There are two solutions to this: 1) (quick and dirty) eliminate the Transaction scopes. This doesn’t do good things for data integrity, but it prevents problems. 2) share the connection and transaction. This requires some extra code. (see this forum post). This may be in later versions of CSLA than the 2.0 documented in my book, but I’m waiting on the 3.5 book rather than having to buy all the supplements AND a new book in the fall.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s