Cadshift

A Reddit thread in r/manufacturing asked how small shops bridge the gap between CAD and production. Twenty-three comments came in — ranging from printed travelers to shared Dropbox folders to custom Fusion 360 dashboards. No two shops described the same system. The only consensus: whatever they’re doing, it’s held together with naming conventions and institutional memory. The CAD-to-production gap is not one problem. It’s four overlapping failures that compound each other, and small fabrication shops feel every one of them because they can’t throw PDM licenses and MES platforms at the problem. ...

Engineers are feeding SolidWorks tasks to ChatGPT, Copilot, and Claude and getting working VBA macros back — sometimes. A Reddit post showing a ChatGPT-generated STL export macro pulled 26 upvotes. A separate thread about building an MCP server for the SolidWorks API drew 15 comments. The interest is real, and for good reason: writing a SolidWorks VBA macro from scratch means wrestling with a COM API that has methods taking 23 parameters and returns boolean values that aren’t actually booleans. ...

You add a Syncfusion data grid to your SolidWorks add-in’s WPF panel. It compiles. The DLLs are in your output folder. You launch SolidWorks, and the add-in loads. Then you open the panel and get this: System.Windows.Markup.XamlParseException: Could not load file or assembly 'Syncfusion.SfGrid.WPF, Version=27.2.2.0, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89' or one of its dependencies. Everything compiled. The DLLs are right there in bin\Debug. NuGet copied them. So why can’t WPF find them? The answer involves a fundamental mismatch between how the .NET CLR probes for assemblies and where COM add-ins actually live on disk. We decompiled SolidWorks’ native add-in loader, examined the WPF BAML reader source code, and inspected the CLR’s assembly resolution pipeline to understand exactly why this happens — and how to fix it with five lines of code. ...

The Hours You’re Not Getting Back Ask any engineer where their time actually goes, and the answer is rarely “designing.” It’s exporting files. Converting formats. Renaming outputs. Running the same five steps in the same order for the twentieth time this month. That’s not a skills problem. It’s a workflow problem — and it’s exactly what CAD automation is built to fix. If you’re a mechanical engineer, CAD manager, or GIS professional who suspects too much of your day is going to work a script could handle, you’re probably right. This article covers what CAD automation actually means in practice, which tasks are worth tackling first, and how engineering teams are using it to reclaim real hours without changing how they design. ...

Large engineering projects create file management nightmares. You start with good intentions—clear naming conventions, organized folders, consistent metadata. Three months later, you’re hunting through folders named “Final_v2_ACTUAL” and files called “bracket_modified_JM_03152026.” Manual file organization breaks down at scale. When your team grows beyond five engineers or your part library exceeds 500 files, human inconsistency creates chaos. Missing parts during assembly reviews. Fabrication delays from incorrect file versions. Hours spent searching for the right DXF. ...

The Real Cost of CAD Data Silos You design in SolidWorks. Your supplier uses Inventor. The fabrication shop runs AutoCAD. Your client wants STEP files, but their downstream partner needs DXFs with specific bend line formatting. Sound familiar? CAD interoperability isn’t just a technical challenge—it’s a business problem that costs engineering teams hours of manual work, creates fabrication delays, and introduces errors that ripple through entire supply chains. When CAD data can’t move cleanly between systems, engineers spend time in export dialogs instead of designing. Fabrication shops get files missing critical metadata. Projects stall while teams manually convert formats and fix translation errors. ...

When You’re Tired of Doing the Same Export Steps on Repeat If you’ve spent any real time looking for ways to automate SolidWorks export workflows, you’ve probably come across both CadShift and CAD+ by Xarial. Both tools aim to cut down the manual grind of repetitive CAD tasks — but they approach the problem from very different angles. This comparison is for engineers actively evaluating both options who want a straight answer: what does each tool actually do, where does each one fall short, and which one makes more sense for your situation. ...

When your engineering team is buried in repetitive CAD tasks, automation stops being a nice-to-have. Two tools tend to come up in that conversation: CadShift and DriveWorks. Both reduce manual work—but they solve very different problems. DriveWorks focuses on design automation, generating new CAD models from rules and parameters. CadShift tackles workflow automation, streamlining the export, conversion, and processing tasks that pile up after your designs are complete. Here’s what you need to know to figure out which one actually fits your team. ...

You click “Fillet,” pick an edge, type a radius, and hit the green check. The edge rounds off. Done. Until it isn’t. Until you get “Fillet operation failed” on a perfectly reasonable-looking edge. Or until the same 2mm radius works on one edge but blows up on the adjacent one. Or until your model rebuilds fine in SolidWorks but the same STEP file fillets differently in Inventor. These aren’t random bugs. They’re the predictable result of three completely different geometric kernels making three completely different decisions about how to roll a ball along an edge. We decompiled the DLLs, read the exported symbols, and walked through the open-source code to see what’s actually happening. ...

The Export Problem Nobody Talks About You’ve finished the design. The model is clean, the drawing is done — and now comes the part nobody put on the project timeline: exporting everything. Open part. Save As. Choose format. Set options. Confirm. Repeat. Forty times. If you’ve spent any real time in SolidWorks, you know this routine. It’s not hard, exactly — it’s just slow, repetitive, and surprisingly easy to get wrong. One bad export setting, one missed bend line, one file dropped in the wrong folder, and suddenly you’re fielding questions from manufacturing because they got bad data. ...