C-Sharp

“SolidWorks automation” covers four distinct things that are often treated as interchangeable. They aren’t. A VBA macro that exports DXF files is automation. So is a Task Scheduler job that runs every night. So is a PDM Dispatch script that triggers on a workflow transition. So is a C# COM add-in with a custom Property Manager Page. Each approach has a specific setup cost, maintenance burden, and capability ceiling. Picking the wrong one for a given workflow creates either an over-engineered solution or one that fails the moment requirements change. This guide maps the decision. ...

Every SolidWorks API developer has spent hours debugging a macro that produces no error, no exception, and completely wrong output. The SolidWorks COM API is old enough that many of its failure modes predate modern error handling conventions — methods that silently return Nothing, boolean flags that are ignored, and side effects that modify document state without warning. This is a catalogue of the seven most common ones. Each has a pattern, a root cause, and a fix. ...

The SolidWorks API speaks one language for lengths: meters. Not millimeters. Not inches. Meters, always, regardless of what your document’s unit system displays. This sounds like something you’d learn in the first chapter of any SolidWorks API tutorial, and it is — yet it causes more silent macro failures than any other single issue. The problem is not that developers don’t know about it. The problem is that it bites you in a second way you didn’t expect, in a context you were already confident about. ...