Hi Richard,
Your post reminded me that we have recently discussed stashing away a copy of the shipped manager in the installation folder (Program Files) so that one always has an easy way to grab it and start fresh. While I understand the usefulness of the 'reset' feature in an ECAP sandbox, it is not as clear how this would function in a multi-installation environment like Environments. There are several issues that make it more difficult.
-Since one may have many different installations managed by Environments, which manager would be used on a 'reset' operation?
-A common scenario in Environments is to connect all development images to a single emsrv controlled manager (containing code for all installed versions of VA Smalltalk) , potentially on a remote machine. Reseting a remote manager would be challenging, as would knowing what manager to replace it with.
Maybe just having a pristine manager in the installation folder would be useful enough to allow you to write your own 'reset' scripts to do what you need? Just food for thought ... open to suggestions!
Regards,
Biob