Transactional design

Question

I need to create a "transactional" process using an external API that does not support COM + or .NET transactions (more precisely, Sharepoint)

I need to do to be able to execute several processes in a sequence, but any failure in this sequence means that I will have to manually undo all the previous steps. In my case, there are only 2 types of steps, both of which are pretty easy to undo / undo.

Are there any suggestions for design or structures that might be useful for this?

Answer 1

SharePoint, , , Update() , SPList.Update() SPWeb.Update().

. 6 Head First Design Patterns , .

Answer 2

GoF .

, ( ).

Answer 3

/ Memento Pattern. .

Answer 4

GOF Command Pattern Transaction Script P EAA.

, ( Script), .

Answer 5

, Compensating Resource Manager:

http://msdn.microsoft.com/en-us/library/8xkdw05k(VS.80).aspx

Answer 6

++ ( ), Scope Guard > , , , .NET, ScopeGuard IDisposable "" .