Cadshift

If you’re building SolidWorks automation or evaluating how existing tools work, the architectural question of in-process versus standalone matters more than most developers initially expect. The choice affects which API calls you can make, how reliably the automation runs, and how much maintenance you’ll do when SolidWorks updates. This is worth understanding whether you’re writing your own add-in or evaluating third-party tools. The Two Execution Models In-process automation runs inside the SolidWorks process. An add-in is a DLL loaded by SolidWorks at startup. When your add-in code runs, it’s in the same memory space as SolidWorks itself. You communicate with the SolidWorks API through a direct object reference — no inter-process communication, no marshaling. ...

You’ve clicked inside that left-hand panel in SolidWorks thousands of times. Every time you create an extrude, add a fillet, define a mate, or configure a sheet metal feature, the Property Manager Page slides in from the left with its groups, checkboxes, selection boxes, and blue highlight fields. It looks like a standard Windows control panel. But it isn’t. If you’ve ever tried to build your own PMP through the SolidWorks API, you’ve noticed something strange: you don’t create Windows controls. You call AddControl with a type enum and get back a COM interface. You can’t set a font. You can’t subclass the window. You can’t attach a debugger to the control’s HWND the way you would with a normal Windows button. The PMP controls don’t behave like anything else on Windows. ...

SolidWorks PDM is doing what it was designed to do: managing file versions, controlling access, and keeping your CAD data from becoming a chaotic mess of part_v3_FINAL_real_final.sldprt files. Most teams that implement it see immediate benefits in file control. But then the engineer emails the shop floor a DXF with a hand-typed filename. Procurement is working from a BOM that was exported two weeks ago. The fabrication team has a different quantity listed than what’s in the current assembly. PDM didn’t prevent any of this. ...

Every major SolidWorks release changes something under the hood that nobody asked for. The 2025 release is no exception, and this time it’s the flat pattern engine that got reworked. If you’ve upgraded recently and noticed that your DXF exports look different, your corner reliefs have mysterious tear lines, or your flatten sub-features are behaving strangely — you’re not imagining things. These are real changes in how SolidWorks 2025 handles sheet metal internally, and they affect anyone who relies on consistent DXF output for fabrication. ...

You just built a SolidWorks add-in. Before it can run, you need to register it as a COM server with regasm.exe, write registry keys under HKEY_LOCAL_MACHINE, and make sure your class has [ComVisible(true)] and a [Guid] attribute. You need admin privileges. You’re locked to .NET Framework 4.x. And if the registration goes wrong, you get a cryptic swRegistrationError and nothing loads. Meanwhile, your colleague building an Inventor add-in drops a .addin XML file into a folder, points it at a .NET 8 assembly, and it just works. No regasm, no registry, no admin rights. ...

The flat pattern comes out wrong. The folded part measures correctly. The DXF dimensions are off by a few millimeters — or sometimes more. Your press brake operator is asking questions you can’t easily answer. This is a K-factor problem, and it’s common enough that manufacturing shops build their own macros to detect it. Understanding why it happens, and how to set SolidWorks up to avoid it, is worth the time for any team doing regular sheet metal work. ...

Every fabrication shop has a corner full of welding jigs. Custom fixtures built for a single assembly, used for a single production run, and then stored indefinitely because throwing away tooling feels wrong even when you know you’ll never use it again. SolidWorks’ Tab and Slot feature offers a fundamentally different approach: design the parts so they locate themselves. Instead of external fixtures holding components in alignment during welding, interlocking geometry cut directly into the sheet metal parts does the positioning for you. ...

There’s a recurring post format in the SolidWorks community that breaks CAD automation into levels: macros, parametric design, API integration, configurators. The comments are always the same — experienced engineers arguing about which level their team is actually at, and why Level 3 is the sweet spot that most teams never reach. They’re right. And understanding why most teams plateau matters if you’re trying to decide where to invest automation effort. ...

Engineers tend to think about DXF quality in terms of geometry accuracy. Does the flat pattern dimension match the folded part? Are the holes in the right positions? Is the file exported at the correct scale? These things matter. But they’re the minimum requirement. Fabricators — particularly laser cutting shops and press brake operators — need significantly more from a DXF file to actually process a part without back-and-forth. The geometry tells them what to cut. Everything else tells them how to do the job. ...

Converting dozens of DWG files to PDF one at a time wastes hours you don’t have. Whether you’re delivering drawings to clients, creating documentation packages, or archiving completed projects, bulk conversion saves time and eliminates repetitive work. This guide covers manual methods and automated solutions for converting DWG files to PDF at scale. You’ll learn when each approach makes sense and how to choose the right workflow for your needs. ...