I’m implementing transaction support for my eventstore usage (initially it passed me by that GES doesn’t enroll in System.Transactions.TransactionScope-style usage so maybe that could be shouted-out in the docs?) and have seen EventStoreTransaction ContinueTransaction(long transactionId). Yes, I use a container with a per-request lifestyle for my connections.
What is the expected use-case for this? I was planning on potentially making multiple writes to a single EventStoreTransaction object reference, but basically apart from calling Commit() when I’m done, the usage isn’t much different to using EventStoreConnection as I have until now.
I guess I’m mostly looking for confirmation that I don’t need ContinueTransaction() in my case, and that there’s a specific reason for it being there.
Thanks in advance,