DevKit distribution as xlam add-in

[navferty]

Currently the instructions include steps like manual import of xlsm_devkit.bas module and running code manually with Alt-F8. Also user should be careful to avoid saving xlsm workbook after import, otherwise devkit code would be included in workbook.

Possible alternative would be to release this devkit as an xlam add-in. This approach would allow delivering it as a single .xlam file. The add-in could also include a ribbon with custom controls, to export any of opened workbooks. It also keeps VBA project of user workbook clear from devkit code itself.

[minipoisson]

Thank you for the idea.

I agree that distributing xlsm_devkit as an XLAM add-in could make the tool much easier to use. Calling the main features from the Ribbon would be much more user-friendly than running macros manually from the VBE, and it would also reduce the risk of accidentally leaving xlsm_devkit's own modules inside the target workbook.

For now, I would like to keep the current .bas-based workflow as a minimal and portable option, especially for restricted business environments. However, I think an XLAM version would be a good additional distribution format for normal development environments.

I will keep this issue open as a future enhancement.