Originally Posted by
dgorsman
dotNET is pretty complex, and I suspect the Action Recorder storage mechanism is much closer to conventional scripting. I'd rather see it produce an XML metadata file describing the steps taken, plus (possibly) an Action Recorder API for dotNET for more complex manipulation. That way the XML content can be consumed by other operations, including LISP and manual tweaking and possibly even direct consumption by the new core console, and also be available from common network locations (unlike DLL; yes, I know about CASPOL but poking holes in the security for the sake of convenience isn't a good idea).