Handle File-Save differently in Development Edition

[jimm-domingo]

There's an issue with a developer accidentally saving the development edition of her toolkit add-in which uses this library. She can trigger the save in the VBE by clicking the Save icon or selecting File --> Save menu item. This is a natural behavior to regularly save one's work to disk.

The problem is that this action causes all the modules that were imported during the bootstrap process to be saved in the development edition. And that's problematic, because the next time the development edition is opened, it will attempt to import those modules again.

So the solution is to handle a Workbook_BeforeSave event handler in the toolkit add-in. This handler could do one of these:

1. Ignore the event, by setting Cancel = True, so the add-in is not saved. But this is a not good option because the developer is expecting the add-in to be saved to disk, and her action is silently ignored without any feedback.
2. Alternatively, display a message telling the developer that the add-in can't be saved, and that instead, she should use Developer Tools --> Export VBA Code menu item.
3. Automatically call the Export VBA Code menu item.
4. Provide a configuration setting that a developer can use to specify that a File-Save will cause either action 2 (display message) or action 3 (call vba-code export).