i need some kind help currently i am working on biztalk server 2004 i have an issue related to transaction handling in following scenario. i have an orchestration that is doing something in an atomic transaction, then it calls a .net component that do something in his own transaction and then commit it and problem starts from here, if later on i do roll back then the work done by .net component does not roll baked. i cant avoid .net components suggest me some solution.
We ran into something like that in the past. If I remember correctly, we ended up changing the transaction type on the .net component to participate in the Atomic transaction that was created inside the Orchestation rather then creating a new one inside the Atomic Transaction.