This is not needed. If the "parent" TransactionScope is Required, the nested one will be enrolled it the transactions already. If it isn't, the nested one will not automatically become "required".
The only exception is if you explicitly set the nested TransactionScope to RequiresNew, when a new transaction will start.
Please note that my usage is that an inner transaction will be having its TransactionScope to suppress by default, but when there is a parent transactionscope, then I need to change this suppress to be inline with the parent transactionscope. Kindly confirm – saravanan Jun 2 at 5:51 @saravanan - If you suppress the inner transaction, it will not participate in a transaction. Perhaps you should create two versions of your function - one suppressing transactions and one not.
– Oded Jun 2 at 5:56 I actually have to use this feature for MySQL & SQL transactions. In case of SQL I will allow the child transaction to participate in the parent transaction. In case of MySQL, it will be in a suppressed transaction as MySQL does not support distributed transactions.
– saravanan Jun 3 at 4:02.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.