AnsweredAssumed Answered

How to fix 'swApp not declared'

Question asked by John Karsten on May 9, 2019
Latest reply on May 10, 2019 by John Karsten

Like • Show 0 Likes0
Comment • 19

Hey guys. I'm building an add-in(used the SW template) and trying to get some simple code to run via a command button. I copied this code from the macro recorder and made some edits, such as removing the 'set' function and adding parenthesis around arguments. I can't figure out how to get rid of the "swApp not declared", "Application not declared" and "SWVerify not declared". I've played around with some statements I've found by searching, but when I run the code, SW just power exits. I think if I can learn how to fix this problem, I can trouble shoot my other VBA macros. I have some nice utilities built using the SW VBA editor. Currently looking for a good book on SW and .NET

Dim Part As Object
Dim boolstatus As Boolean

swApp = Application.SldWorks

Part = swApp.ActiveDoc
boolstatus = Part.Extension.SelectByID2("Front Plane", "PLANE", 0, 0, 0, False, 0, Nothing, 0)
Part.SketchManager.InsertSketch(True)
Part.ClearSelection2(True)
Dim skSegment As Object
skSegment = Part.SketchManager.CreateCircle(0#, 0#, 0#, 0.019991, 0.015967, 0#)

Jim Sculley May 10, 2019 10:40 AM

Correct Answer

John Karsten wrote:

Jim, I've gotten that far.
Here's what I'm trying to figure out.

...

...
...
So, this is not code I wrote. It's the cube code from the beginner template. It generates an error that says iSwapp is not declared.
I added Dim iSwApp As SldWorks to get rid of the error.

You didn't get rid of the actual error. You simply added a variable declaration to keep the compiler quiet. Think of variables as envelopes. In the ConnectToSW method of the addin, SOLIDWORKS puts a letter (object) in the iSwApp envelope (variable). The letter is the actual SOLIDWORKS object your addin is connected to. If you declare a variable named iSwApp in your Form1 class, it is not the same envelope. It is just a new, empty envelope. It doesn't have a letter in it. You can't read from it or write to it. There is nothing there. In order to make your Form1 class aware of the SOLIDWORKS object, you need to make a copy of the letter and put it in the envelope in Form 1. The easiest way to do it is to add a constructor in Form1 that takes an argument:

Public Class Form1
Dim mySWApp As SldWorks.SldWorks 'an empty envelope

   Public Sub New(ByVal swApp As SldWorks.SldWorks)
      mySWApp = swApp 'put the copy of the letter in the envelope
      InitializeComponent()
End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
   Dim mDoc As ModelDoc2
   mDoc = mySWApp.ActiveDoc
   MessageBox.Show(mDoc.GetTitle())
   End Sub
End Class

Then in your code that creates the form, you pass in the object:

Dim myForm As New Form1(iSwApp)
myForm.Show()

See the reply in context

No one else had this question

Outcomes

19 Replies

John Karsten May 9, 2019 9:26 AM
Mark Correct
Correct Answer
So I read about the VSTA and used it to translate the recorded macro. No errors in Visual Studio, but again, when I try to run the code from VS, SolidWorks just blows up. If I open SW and try to run the code, I get an error "Object reference not set to an instance of an object". New code below. Still digging.........

Public Class Form1
Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
Dim swDoc As ModelDoc2 = Nothing
Dim swPart As PartDoc = Nothing
Dim swDrawing As DrawingDoc = Nothing
Dim swAssembly As AssemblyDoc = Nothing
Dim boolstatus As Boolean = False
Dim longstatus As Integer = 0
Dim longwarnings As Integer = 0
swDoc = CType(swApp.ActiveDoc, ModelDoc2)
boolstatus = swDoc.Extension.SelectByID2("Front Plane", "PLANE", 0, 0, 0, False, 0, Nothing, 0)
swDoc.SketchManager.InsertSketch(True)
swDoc.ClearSelection2(True)
Dim skSegment As SketchSegment = Nothing
skSegment = CType(swDoc.SketchManager.CreateCircle(0, 0, 0, 0.019472, 0.014409, 0), SketchSegment)
swDoc.ClearSelection2(True)
swDoc.SketchManager.InsertSketch(True)
End Sub
Public swApp As SldWorks
End Class
Like • Show 0 Likes0
Actions
Kevin Chandler May 9, 2019 12:25 PM
Mark Correct
Correct Answer
Hello,

This is in VBA, but I'm not seeing explicit declarations as SW bits such as shown here:

Are these required for your project?

Kevin
Like • Show 0 Likes0
Actions
- John Karsten @ Kevin Chandler on May 9, 2019 2:39 PM
  Mark Correct
  Correct Answer
  Hey Kevin. I believe those are for VBA. They don't seem to work in visual studio. I even copied some sample code from the API help section for .NET, run the code from VS, SW loads, click command button and SW just disappears. Restart SW outside of visual studio, press command button and get error 'Object reference not set to an instance of an object'.
  I can't figure out what it's barking about. Seems like sample code should run. How do I get visual studio to talk to SW?
  This sample code blows up SW as soon as it hits the first line after declaring variables. I commented out the rest.
  Public Class Form1
  Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
  Dim swModel As ModelDoc2
  Dim swModelDocExt As ModelDocExtension
  Dim swSketchSegment As SketchSegment
  Dim swSketchManager As SketchManager
  Dim swFeatureManager As FeatureManager
  Dim swFeature As Feature
  Dim status As Boolean
  
  swModel = swApp.NewDocument("C:\ProgramData\SolidWorks\SOLIDWORKS 2017\templates\Part.prtdot", 0, 0, 0)
  'swModelDocExt = swModel.Extension
  'swSketchManager = swModel.SketchManager
  'swFeatureManager = swModel.FeatureManager
  
  There was a lot more code here.........
  
  End Sub
  Public swApp As SldWorks
  End Class
  Like • Show 0 Likes0
  Actions
  - Frederick Law @ John Karsten on May 9, 2019 2:48 PM
    Mark Correct
    Correct Answer
    Attached SW addin VB template.
    Attachments
    swvbaddin2018.zip17.3 KB
    Like • Show 0 Likes0
    Actions
    - John Karsten @ Frederick Law on May 9, 2019 3:39 PM
      Mark Correct
      Correct Answer
      Well, I already had a template loaded in, but removed it and tried your attached one. Created a new project. Still the same result. Imports are at the top of the screen. Code copied from API examples.
      Like • Show 0 Likes0
      Actions
      - Frederick Law @ John Karsten on May 9, 2019 4:05 PM
        Mark Correct
        Correct Answer
        I can build the Project without error.
        
        In the Project SwApp is decleared:
        
        ReadOnly Property SwApp() As SldWorks
        Get
        Return iSwApp
        End Get
        End Property
        
        Are you building add-in or macro?
        The codes are completely different.
        
        Where did you declare SwApp?
        Like • Show 0 Likes0
        Actions
  - Jim Sculley @ John Karsten on May 9, 2019 4:43 PM
    Mark Correct
    Correct Answer
    John Karsten wrote:
    
    I can't figure out what it's barking about. Seems like sample code should run. How do I get visual studio to talk to SW?
    This sample code blows up SW as soon as it hits the first line after declaring variables.
    Of course it blows up. You can't create a new class (Form1) and expect it to know anything about the swApp variable declared in a different class. You have to pass that information to it somehow via a property or constructor.
    
    You seem to be flailing about, throwing a bunch of stuff at the wall to see what sticks. What are you actually trying to do?
    
    Macros are different from add-ins are different from standalone apps.
    Like • Show 1 Like1
    Actions
    - John Karsten @ Jim Sculley on May 10, 2019 5:55 AM
      Mark Correct
      Correct Answer
      Jim, no need for all that nonsense. If you don't wanna help someone learn, move along. Maybe one day we'll all be as smart as you. Thanks for playing.
      Like • Show 0 Likes0
      Actions
      - Frederick Law @ John Karsten on May 10, 2019 8:30 AM
        Mark Correct
        Correct Answer
        You figure out how to declare a variable yet?
        Just saying.
        The error is elemental. It shouldn't take a day to figure out.
        Like • Show 0 Likes0
        Actions
        John Karsten @ Frederick Law on May 10, 2019 9:16 AM
        Mark Correct
        Correct Answer
        Frederick, I moved Public swApp As SldWorks inside the sub and still no go. In fact, if you look at sample code on the SolidWorks API help, they call it the way I have it.
        No so elemental, just saying........
        Like • Show 0 Likes0
        Actions
        Frederick Law @ John Karsten on May 10, 2019 9:20 AM
        Mark Correct
        Correct Answer
        Lesson number 97834857783:
        Code in API help doesn't work all the time.
        
        I don't think the problem is API or SW.
        What did you program before this?
        Like • Show 0 Likes0
        Actions
        John Karsten @ Frederick Law on May 10, 2019 9:47 AM
        Mark Correct
        Correct Answer
        Have a nice day Fred
        Like • Show 1 Like1
        Actions
        Frederick Law @ John Karsten on May 10, 2019 9:53 AM
        Mark Correct
        Correct Answer
        Always.
        
        When someone post a question, we don't know how much they know or what their skill level is.
        We keep guessing from their question and their response.
        
        Of course we could guess wrong.
        
        I need some popcorn.
        Like • Show 0 Likes0
        Actions
      - Jim Sculley @ John Karsten on May 10, 2019 9:07 AM
        Mark Correct
        Correct Answer
        In your first post, you said you were building and add-in using the SW template in Visual Studio. You then posted a screenshot of code that is definitely not part of an add-in. You then said you read about VSTA and used that to translate a macro and posted some code that is definitely not the code for a working macro. Next you said you copied some code from the API Help, but without knowing which example and for what type of utility (add-in, macro, standalone app) there is no way for anyone to diagnose the issue.
        
        So, once again, stop flailing about and tell us exactly what you are trying to accomplish.
        
        Do you want to make an add-in, a macro or a standalone application?
        
        If you are trying to convert a bunch of existing macros to VB.NET, take one of your working macros, the smaller the better, and post it here. In full. A complete working example. Not bits and pieces.
        
        Macro collections are usually best handled by turning them into an add-in. The SW add-in template for Visual Studio creates a working add-in out of the box with no code additions from you.
        
        File...New.....Project...SwVBAddin
        
        Build Project.
        
        Debug. SOLIDWORKS should start.
        
        Open a new part.
        
        There should be a new command tab (VB Addin) with 4 icons on your command bar:
        
        Click the leftmost one.
        
        SOLIDWORKS will create a cube:
        
        Only if that works should you begin adding your own code.
        Like • Show 1 Like1
        Actions
        John Karsten @ Jim Sculley on May 10, 2019 9:45 AM
        Mark Correct
        Correct Answer
        Jim, I've gotten that far.
        Here's what I'm trying to figure out.
        Call on a user form via a new command I added to the menu:
        
        #Region "UI Callbacks"
        Sub Form()
        Dim F As New Form1()
        F.Show()
        End Sub
        
        Add command button in the user form and add the cube code to command button(Like I do in VBA)
        
        Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
        'make sure we have a part open
        Dim partTemplate As String
        Dim model As ModelDoc2
        Dim featMan As FeatureManager
        partTemplate = iSwApp.GetUserPreferenceStringValue(swUserPreferenceStringValue_e.swDefaultTemplatePart)
        If Not partTemplate = "" Then
        model = iSwApp.NewDocument(partTemplate, swDwgPaperSizes_e.swDwgPaperA2size, 0.0, 0.0)
        model.InsertSketch2(True)
        model.SketchRectangle(0, 0, 0, 0.1, 0.1, 0.1, False)
        'Extrude the sketch
        featMan = model.FeatureManager
        featMan.FeatureExtrusion(True,
        False, False,
        swEndConditions_e.swEndCondBlind, swEndConditions_e.swEndCondBlind,
        0.1, 0.0,
        False, False,
        False, False,
        0.0, 0.0,
        False, False,
        False, False,
        True,
        False, False)
        Else
        System.Windows.Forms.MessageBox.Show("There is no part template available. Please check your options and make sure there is a part template selected, or select a new part template.")
        End If
        End Sub
        
        So, this is not code I wrote. It's the cube code from the beginner template. It generates an error that says iSwapp is not declared.
        I added Dim iSwApp As SldWorks to get rid of the error. The user form displays, I click the command button and SolidWorks exits.
        Why won't the command button execute code that was copied from a section that WILL run it? What am I missing in the command button to make it 'hook'?
        Like • Show 0 Likes0
        Actions
        Jim Sculley @ John Karsten on May 10, 2019 10:40 AM
        Unmark Correct
        Correct Answer
        John Karsten wrote:
        
        Jim, I've gotten that far.
        Here's what I'm trying to figure out.
        
        ...
        ...
        ...
        So, this is not code I wrote. It's the cube code from the beginner template. It generates an error that says iSwapp is not declared.
        I added Dim iSwApp As SldWorks to get rid of the error.
        You didn't get rid of the actual error. You simply added a variable declaration to keep the compiler quiet. Think of variables as envelopes. In the ConnectToSW method of the addin, SOLIDWORKS puts a letter (object) in the iSwApp envelope (variable). The letter is the actual SOLIDWORKS object your addin is connected to. If you declare a variable named iSwApp in your Form1 class, it is not the same envelope. It is just a new, empty envelope. It doesn't have a letter in it. You can't read from it or write to it. There is nothing there. In order to make your Form1 class aware of the SOLIDWORKS object, you need to make a copy of the letter and put it in the envelope in Form 1. The easiest way to do it is to add a constructor in Form1 that takes an argument:
        
        Public Class Form1
           Dim mySWApp As SldWorks.SldWorks 'an empty envelope
           Public Sub New(ByVal swApp As SldWorks.SldWorks)
              mySWApp = swApp 'put the copy of the letter in the envelope
              InitializeComponent()
        End Sub
        
        Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
           Dim mDoc As ModelDoc2
           mDoc = mySWApp.ActiveDoc
           MessageBox.Show(mDoc.GetTitle())
           End Sub
        End Class
        
        Then in your code that creates the form, you pass in the object:
        
        Dim myForm As New Form1(iSwApp)
        myForm.Show()
        Like • Show 0 Likes0
        Actions
        John Karsten @ Jim Sculley on May 10, 2019 12:03 PM
        Mark Correct
        Correct Answer
        Jim, that's perfect!
        I completely understand everything you said and was able to get the cube code to run via the command button.
        The way you set up 'mySWApp' is the link I was missing.
        Thanks, and have a great weekend, Sir.
        Like • Show 0 Likes0
        Actions
  - Frederick Law @ John Karsten on May 9, 2019 4:51 PM
    Mark Correct
    Correct Answer
    John Karsten wrote:
    
    Public Class Form1
    Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
    Dim swModel As ModelDoc2
    Dim swModelDocExt As ModelDocExtension
    Dim swSketchSegment As SketchSegment
    Dim swSketchManager As SketchManager
    Dim swFeatureManager As FeatureManager
    Dim swFeature As Feature
    Dim status As Boolean
    
    swModel = swApp.NewDocument("C:\ProgramData\SolidWorks\SOLIDWORKS 2017\templates\Part.prtdot", 0, 0, 0)
    'swModelDocExt = swModel.Extension
    'swSketchManager = swModel.SketchManager
    'swFeatureManager = swModel.FeatureManager
    
    End Sub
    Public swApp As SldWorks
    End Class
    You declare swApp after the sub.
    Either move it before or inside the sub.
    Like • Show 0 Likes0
    Actions
Artem Taturevych May 9, 2019 4:44 PM
Mark Correct
Correct Answer
If you want to create stand-alone application, like windows forms. Read this article: How to create stand-alone (exe) applications using SOLIDWORKS API

You can also use .Net VSTA macros: Create And Run VSTA Macro (C# and VB.NET) in SOLIDWORKS

For add-ins, read this article: How to develop add-ins for SOLIDWORKS automation via API

If you want to make addins in a simpler way that default sdk, look at this framework: Introduction of SwEx Framework for advanced development of SOLIDWORKS add-ins

I would recommend starting with stand-alone applications before moving to addins.

Edit: also couple of video tutorials:
SolidWorks API Stand-Alone Application - YouTube
Create and register SolidWoks C# and VB.NET AddIns in 3 Steps - YouTube
Like • Show 2 Likes2
Actions

How to fix 'swApp not declared'

Outcomes

Attachments

Related Content

Recommended Content