It seems that SqlCommandBuilder.DeriveParameters will not participate in a transaction when the SqlCommand that it uses has a transaction assigned to it.

This can be a real PITA to track down when combined with the Data Application Block's parameter caching. I pulled my hair out for two days isolating this sucker.