Joerg Jooss said:
Just to get this straight: You need a .NET FCL class that implements the
Command pattern?
I don't know one by heart, but since the pattern is most often applied with
application architecture components, I'm not really surprised.
Cheers,
Hi,
http://www.dofactory.com/Patterns/PatternCommand.aspx
It depends on how you define 'command pattern', usually, we are
talking about recording a 'step' performed. A command records a state
change between two states. Usually, this is done with a do() which
executes the change and an undo() which allows you to reverse the
change. Thus any application with numerous do/undo would be a good
example.
Application wise, you see this in:
VS.NET REDO/UNDO, Bookmarks (Forward/Back)
Office REDO/UNDO
Photoshop also has a pretty amazing REDO/UNDO thing.
In the .NET Framework Library, I'd say the IDBCommand (and all the
children) are examples of the command pattern. (Although they aren't
usually chained together like in a multi- undo/re-do example. I
suppose you can say that you open a connection/transaction and run
multiple commands and it's the same scenario.
jliu -
www.ssw.com.au -
www.johnliu.net