U225X PUBLIC-SAFE CONVERSATION NOTE

RECORD: CHAT-0317
TOPIC: SOLIDWORKS Add-In Guidance
IMPORTED: 2026.05.11

This note was generated from a matching conversation in the supplied ChatGPT export.
EXTRACTED REQUEST: So I have been creating forms in vba for solid works they work great for what I do but is there a better way to create some of these macros I have been making and giving them a more professional look and also the install of them isn't too bad but it still relys on the user copying files and editing IT would be nice if they had an install file or could load an add in

RECOVERED CONVERSATION EXCERPTS
USER MESSAGES:
1. So I have been creating forms in vba for solid works they work great for what I do but is there a better way to create some of these macros I have been making and giving them a more professional look and also the install of them isn't too bad but it still relys on the user copying files and editing IT would be nice if they had an install file or could load an add in
2. What would i need to start converting some of these to VB.net
3. SO what programs do I need to download to get started in this
4. how do i check if SOLIDWORKS API SDK is installed

ASSISTANT RESPONSES:
1. You’re basically at the point where your VBA tools are becoming an internal product. The next step is less about “better macros” and more about packaging, UI, deployment, and version control.
2. Yes. For what you’re building, the better long-term route is a SOLIDWORKS Add-In, not loose `.swp` VBA macros. Best path: 1. Keep VBA for quick tools Great for testing ideas, one-off macros, and personal automation. 2. Move serious tools to a VB.NET or C# SOLIDWORKS Add-In SOLIDWORKS provides Visual Studio add-in templates for C# and VB.NET, and the API SDK supports building add-ins directly. [embedded media omitted] Benefits: - Professional dockable panels / task panes - Better-looking forms than VBA UserForms - Buttons inside SOLIDWORKS CommandManager - Central settings/config files - Easier version control - Can be installed like normal software - Can auto-load when SOLIDWORKS starts - Less “copy this file…
3. That screenshot tells me the API SDK likely is NOT installed, or at minimum the API components were not fully installed. Normally you would also see folders like: [code excerpt omitted] or: [code excerpt omitted] under: [code excerpt omitted] Next Step Open: [code excerpt omitted] Then: [code excerpt omitted] When you get to the product/component tree: Look for: [code excerpt omitted] and check it. You may also see: - API Help Files - API Examples - VBA SDK tools Install all of those.. After Install You should end up with folders like: [code excerpt omitted] and/or [code excerpt omitted]. Then Install Visual Studio Once both are installed: 1. Open Visual Studio 2. Create New Project 3. Search: [code excerpt om…

EXTRACTED KNOWLEDGE / HOW-TO
- *1. Keep VBA for quick tools
- *2. Move serious tools to a VB.NET or C# SOLIDWORKS Add-In
- Professional dockable panels / task panes
- Better-looking forms than VBA UserForms
- Buttons inside SOLIDWORKS CommandManager
- Central settings/config files
- Easier version control
- Can be installed like normal software
CONVERSATION SHAPE: 4 user turns / 7 assistant turns
ATTACHMENTS DETECTED: 14

Raw transcripts, private details, exact locations, account information, employer/customer-confidential material, and restricted software references are not published in this note.
PROPERTY OF U225X / PUBLIC-SAFE IMPORT