Strategy for registering / unregistering shell extensions #5
Description
Shell uses an extension.json file in order to correctly parse extension command line parameters. Today, while we are still in active development of the extension model. we are populating this file by hand. Once we have locked down the extension model, we will need a more developer-friendly approach to extension registration management.
Ideally, extensions would register themselves on install and unregister when uninstalled. However, it may be cumbersome to require an installer for extensions - esp since they have to work across the platforms neo-shell supports. Maybe extensions should implement standard "register" and "unregister" commands. This approach has it's own issues. For example, Shell would need to clean up extensions that have been removed w/o the developer calling the unregister command.