Checkpoint Library for C #

I am looking for a checkpoint library for C #. Any ideas?

see http://en.wikipedia.org/wiki/Application_checkpointing

+2
c #
Nov 30 '08 at 17:00
source share
4 answers

This should be possible to implement using transactions (commit / rollback) or undo. If you develop your classes and operations correctly, this will work, for this you will need some hard work and discipline using the classes. You should also be careful about exceptions.

The System.Transactions namespace (as suggested by Rune) seems like a good candidate, or at least a good starting point.

+2
Dec 01 '08 at 8:07
source share
β€” -

If I understand you correctly (and the question is rather vague, so I'm not at all sure about this), then the Windows Workflow Foundation certainly has this feature. However, it almost certainly overwhelms what you are asking for.




Well, you added a link that better explains what you mean by a breakpoint.

With this in mind, .Net has nothing built in to support this directly. However, everything that uses a state machine on which a state machine can be stored can be checked / verified, and the transaction has a natural built-in look. WWF is one example of this.

+1
Nov 30 '08 at 19:49
source share

I don't think there is built-in support in this, but you should be relatively easy to build your own. Assuming you have a central application class in which your applications are stored, or at least the part used at the breakpoint. Then you can use serialization to keep the state of your application when necessary. In addition, it would be easy to save snapshots in the file database if you need it later. But for this you will need to write your own library.

As I write this, I begin to feel that there should be some support in this structure. Take a look, for example, at the System.Transactions namespace.

+1
Dec 01 '08 at 7:51
source share

Given the link from wikipedia, I can say that .NET / CLR does not support this. This makes this impossible because .NET does not allow you to check for changes in the application stack, which, in turn, is not possible due to the built-in security in .NET.

0
Dec 01 '08 at 5:43
source share



All Articles