A SolidWorks macro is not an alternative to the API — it runs on it. Where the real line sits, what a macro handles well, and 8 signs you need an add-in.
SolidWorks add-in development in C#: the ISwAddin lifecycle, COM registration, CommandManager and TaskPane, event traps, and 8 mistakes that surface later.
AI speeds up add-in scaffolding and API discovery, then gets COM lifetimes, version signatures and silent failures confidently wrong. Where I draw the line.