The show notes for this Polymorphic Podcast could keep me in fun reading for a few weeks.
It’s pretty easy to make a class into a template. Not everything get’s magicified, but it works and saves time. There’s some discussion of this in this forum post
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.
Master Pages: Tips, Tricks, and Traps: You’d think master pages were self-explanatory, but there end up being things you need to be wary of or work carefully around. This article is a very helpful summary of a number of those hazards.