Forum Discussion
Making an add on
How do I turn this into an add on?
Many thanks
Miles
13 Replies
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
- Thanks for your response. Do you have any idiot primers on the licencing question and the use of visual studio? If the code is open source does that mean people can copy it and circumvent any licencing?? I've previously sorted out a licencing solution for an Excel based product (SummaryPro) which I use to produce summary plans driven directly by plan data but I don't think this will work for project VBA.
Many thanks
MilesYears 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?
