Hi All,
I am in the process of writing Macro's and Add-in's tostandardiseand automate practices within my organisation. There aremany different tasks and jobs that are required andI am worriedthat every one will need to be maintained on eachrelease ofSolidWorks.

What are your experiences with keepingMacro's/Add-in's"future proof".  I will be focussing onwritingAdd-in's for better integration and security, but will theyfallover after each upgrade?

Thanks in advance for you replies.

Cheers,
EricSolidworksApi macros