I just ran into trouble trying to execute some very basic samples from the first chapter of the manual because in-memory provider doesn't support rollback. Wouldn't it be nice to throw informative exception when one tries to create nested transaction since it's not really supported?

If it's too much of trouble to prohibit customer from execute valid code for standalone provider because it's such an important usecase, might just throw that informative exception when actual rollback has to occure?

I mean

var nestedScope = Transaction.Open(TransactionOpenMode.New);
// As we rollback on in-memory provider throw here
nestedScope.Dispose();

This thread was imported from our support forum. The original discussion may contain more detailed answer. Original topic by marmon.