Forum Discussion
Making an add on
If your VBA macro is attached to a specific file, I suggest you use the Organizer to transfer the module containing the macro to your Global. That will make it available to any Project you open or create. You can transfer the macro to other users by simply sending them the file, or a dummy file (e.g. one task), with the macro. I use that method when sending macros I create to someone.
As far as selling your code, that's a little more involved. The first thing to consider is what type of licensing agreement do you want. The second is, will your code be open-source. Third, how will you control configuration. If you want to truly make an add-in (i.e. closed-source), you need to re-create your macro in Visual Studio (or equivalent) so it is a separate entity.
Hope this helps.
John
Many thanks
Miles
Years ago I looked at licensing templates but in the end decided to write my own, but then my code is open-source so licensing is solely dependent on the integrity of users who pay the license fee. If you have something you did for Excel, you might consider using that.
And yes, open-source means anyone, with the right knowledge, can modify the code and do with it whatever they want.
I've never used Visual Studio myself, so I suggest you post a query in the Visual Studio forum, you'll likely find others who had similar questions.
Just curious, what exactly does your Project macro do?
- My macro outputs all calendar exceptions and non standard calendars allowing you to output the holidays which have been entered for each resource in the plan. This is especially useful on a large project when you can put people's holidays into the plan to take advantage of the scheduling capabilities in project without the disadvantage of the rather hidden nature of the holidays saved into the individual resource calendars.
Just for reference I wrote (or updated) a couple of macros that do the same thing and I "published" them on previous versions of this or other Project forums. The macros export Project and resource calendar exceptions data to Excel. Wanna give them a test run?