2016 November 14th
I have seen the same situation many times now in my career as a VBA Developer about how source code control is managed with VBA projects.
Source control on VBA has long been a bit of a nonsense, there isn't any really. When I started my first developer role it was talked about in my team why we don't use it and the best efforts the team did at the time was save the new version to a different folder location and to compare changes in the code from a previous version meant getting a text compare app copy pasting the code into it from the two different versions so you could track what was changed.
My colleague at the time and now very good friend Paul Crook came up with the base of what I have done with the VBA IDE Code Export tool I have just extended some parts of his base that I feel were needed.
What was lacking from Crookie's code, which I brought up at the time
with him was that it only exported
I did ask about code contained within the
ThisWorkbook and the
Sheet* modules. What we decided to do was if there was code in those
modules was to abstract it out into its own module, so
would call out to
ThisWorkbook.bas this was a bit of extra work to
begin with but ultimately benefited us in the long run with good
I wasn't keen on how you had to work with this so decided to have a play around with it when I put it on GitHub I decided to try right some of that, I think I may have made some things worse but I'm keen to make another revision of the tool in the future to correct that.
.conffile to save the project contents to meaning there were no modules left in the project after export