AnsweredAssumed Answered

Time to learn programming. -> strengthened from the crisis

Question asked by Hansjörg Wolff on Apr 23, 2020
Latest reply on Jun 11, 2020 by Matthew Cempa

Like • Show 5 Likes5
Comment • 27

Hello,

i just start to improve my skills in programming makros. In the past i use vba for my macros. But i did not realy programm the macros. Most of them i copy code from macros i found in the forum and then use trail and error as long the macro works in the way i need.

I decided to use vb.net for my new macros. Therefore i bought the book "Automating Solidworks 2019 using Macros" from @Mike Spens.

Maybe there are some comrade-in-arms and we can build a small group to help each other.

I started my selfeducation today with a lot of ambition, but within a short time i run 3 times in trouble.

1. Problem
Fundamentals - (Page 5)
Create a New Macro. Wenn i try to save the "empty" Macro i got following Message:
"Solidworks Visual Studio Tools for Applications

No Visual Studio template Information found. See the application log in Event Viewer for more details...."

This happens with disabled VSTA Version 3.0 checkbox in the SWX Systemoption.
After that SWX hangs and i have to kill it.

2. Problem
I enabled the VSTA 3.0 checkbox in the SWX Systemoption.
Ok now i can save the macro and also open in the MS Visual Studio Community 2015.
According to page 7 i should have 3 references to the Solidworks libraries. In my case i have only 2. The referenc :"SolidWorks.Proxy.Solidworks" is missing.

3. Problem.

i added the code to create the legendary "Hello World" Code.

Wenn i try to run the macro i got following error message:" You can not debug or run the project, because the needed version of Microsoft Office Application is not installed."

Thats a lot of failure for the beginning :-(. Can anybody tell me whats the reason for this Problems?

Stay healthy

No one else has this question

Outcomes

27 Replies

1 2FirstPrevious

Peter Brinkhuis Apr 24, 2020 4:34 PM
Mark Correct
Correct Answer
Have you installed VSTA when installing SolidWorks? Apparently you need to, and you cannot add it afterwards without removing SolidWorks.

I have never worked with vsta macros though, I went straight from VBA to C# in Visual Studio and I have no regrets These videos and SolidDna really helped me to get started:
SolidWorks API (C# SolidDNA) - YouTube
Like • Show 2 Likes2
Actions
Artem Taturevych Apr 24, 2020 6:37 PM
Mark Correct
Correct Answer
Check the log in the event viewer. It should show you how to reset your VSTA templates (I believe there is a command line call you need to do). From my experience VSTA is sometimes tricky. Unfortunately I do not have Mike's book, but I think most of the examples you can apply in stand-alone or add-in applications avoiding use of VSTA macros and it would have pretty much the same effect. It won't be macros though, but APIs work in the same way across different types of applications so you still can follow Mike's book tutorials.

Repairing of SOLIDWORKS might also fix the VSTA issue. Or just contact your VAR - they should be able to help you out.
Like • Show 1 Like1
Actions
Casey Balderson Apr 26, 2020 1:18 PM
Mark Correct
Correct Answer
I was much like you when I started down this route late last year. I heard from everyone to skip VSTA macros and just go straight to an Add-In or Standalone. I ignored them because I felt that VSTA macros was a necessary stepping stone to understand advanced programming. I was wrong.
VSTA macros almost hold you back from unleashing the full potential of programming SolidWorks, while also providing another layer of problems (like the ones you're dealing with). And if you choose to program in VB.NET, you can use Visual Studio, and your recorded VBA Macros will pretty much give you all this information you need when you're trying to record a process. I personally chose C#, because it's the trend, and lends itself well outside of just SolidWorks, including Javascript similarities. (converter.telerik.com/ is great for transition from VB to C#).
A VB.NET standalone allows you to function just like a Macro, and there's so much more you can do. Then if you choose to proceed with an Add-In, all of your existing code and be copied to the standalone very easily.
And, if you want to create a "Macro Button" to your standalone, just follow this tutorial to call the EXE of your standalone.
I know this isn't the answer you were looking for, but I couldn't resist when I saw a mirror image of myself from 10 months ago, and I just wish I could go back and tell myself this information.
Like • Show 4 Likes4
Actions
Peter Brinkhuis @ Casey Balderson on Apr 30, 2020 5:28 AM
Mark Correct
Correct Answer
Thanks for sharing your experience. If it doesn't helper the topic starter now, it will help someone in the future.
Like • Show 1 Like1
Actions
Hansjörg Wolff @ Peter Brinkhuis on Apr 30, 2020 6:51 AM
Mark Correct
Correct Answer
Sorry for the delay, i have to do some preparatory work for a new project. I hope i can deal with the "learning" project at end of this week.
Like • Show 1 Like1
Actions
Hansjörg Wolff May 1, 2020 1:09 PM
Mark Correct
Correct Answer
Hello to all, here i am back again.

First of all thanks to all for the support und the hint´s.
After reading all the hint´s and a conversation with my var i am totally confused.
At the moment i opened this thread i was sure i am on a good way.
Now i am not sure if VSTA is the way i want to go. Or better i should go.

I never bevor had contact with c#.
So i look in the web for literatur and manuals.
I check the version the Visualstudio 2015 is working with. (Because this Version is necessary to interact with SWX2019)
I found a introducing in c# 6 from at the Homepage of University Trier.
I start to read the manual, but for me C# looks verry cryptically.

I also studied the comparison table from Artem.

My Var (he don´t solve my issue with the software) he only give mit the hint: Don´t use VSTA, stay at VBA,
because VBA is more stable and most of the samples are available in VBA.

So, i have to meet a decission.
My first decission: VSTA is out!

But which language i should learn?
I take additional look in the web an search for for C# manuals in the usage together with SWX.
There are the videos from Luke Mallpass from the link peter had posted
I found another video serie from Solidworks Akademy
but i don't know and don't unterstand the language spoken in the video.

Also i found the free books from Luke Mallpass
In his first book he solve all the jobs with VBA and C#.
But the exercises and solution are created with SWX 2008.

So, what shall i do?

I think learning with youtube video's becomes difficult.
No chance to add notes to a chapter, no possibility to use a translater if a used word is not known.

Use the free books from Luke Mallpass, but maybe in new SWX Version the code is different.

Use the book from Mike Spence and try to solve the exercises in VB.Net standalone Makros and not in VSTA?

I think the last solution is the best to go on with the project.

What do you think about?

Regards, and lot of thanks again for all the hint´s

P.S.
I know this isn't the answer you were looking for,....
Casey that´s not true. Your answer and your experience is exakt i'm look for. Why should I repeat the bad experience that others had done long time before my try?
Like • Show 1 Like1
Actions
Matthew Cempa @ Hansjörg Wolff on May 1, 2020 2:25 PM
Mark Correct
Correct Answer
well if you are starting with VBA then I would suggest using VB.net since the syntax is nearly interchangable and you can generally copy VBA code into vb.net with only minor modifications to get started. Once you learn the SWX API then you can work on C# if you like.
Like • Show 3 Likes3
Actions
Casey Balderson May 1, 2020 2:38 PM
Mark Correct
Correct Answer
Yes, I agree with Matthew Cempa. Use VB.net. It will give you the same functionality that C# gives you for the most part, but with the familiar syntax of VBA.
C# is one of the more common languages, and syntax is similar to Javascript (or AppScript for Google). VB.net is still widely used, and you can live-debug with it as well (meaning you can write/modify code while running that code). You cannot live debug with C#, but again, small learning curve for JavaScript programmers. In the end, it's all object-oriented programming. And it's understanding the SolidWorks API that takes the most time. VB.net and C# are both .NET languages, so they interact the same. The goal is just more about having additional functionality over VBA.
Like • Show 3 Likes3
Actions
Amen Allah Jlili May 1, 2020 5:22 PM
Mark Correct
Correct Answer
I think CADSharp.com is the place to go to learn API. Obviously I'm biased so take my word with a grain of salt but feel free to ask our user community. We have more than 10 thousands registered users.

Best,
Amen
Like • Show 2 Likes2
Actions
Artem Taturevych May 1, 2020 5:51 PM
Mark Correct
Correct Answer
Hansjörg,

I would approach your task from 2 perspectives:
- Learning SOLIDWORKS API
- Learning programming
For learning programming in general (if you are planning to build large applications, use some modern technologies and framework, go beyond simple desktop app), I would go with C#. I personally use C# for all my projects. C# and VB.NET are compiled to the same IL language. You have a lot of converters between those two which will give you nearly 100% of accuracy. But C# is way more compact (I would spend about 10-20% less time to develop the same simple app) due to Visual Studio IDE is more adapted to c# than VB.NET and I just need less typing in C#. Furthermore all of the tutorials and videos for great features offered by .NET in nowadays are mainly in C#: WPF for rich UI capabilities, Xamarin for cross-platform mobile development, .NET Core and ASP.NET Core for cross-platform desktop/web development, Blazor for web assembly, ML.NET for machine learning etc. etc. Although you can still use VB.NET for those technologies you will hardly find an example in this language. But as I said - just a matter of taste as both languages cover the same capabilities. The best book you can buy to learn C# IMHO is https://www.amazon.com/CLR-via-4th-Developer-Reference/dp/0735667454 .

If you want to learn SOLIDWORKS API you can go with VBA macros. The majority of examples available on the web for SW API is VBA. This is a reason why most of the examples I put on codestack.net is VBA. Furthermore, I'm finding it simple to play with VBA when I need to tune certain SW API. Even now when I develop in C#, sometimes I create a quick VBA macro to test certain things. You can do this in C#/VB.NET as well by using stand-alone app, but this is a bit slower to run.

Once you learn one programming language, another language is not a problem.

Casey,
>>You cannot live debug with C#
I believe you are talking about the Edit and Continue. You can use it in C# as well.
Like • Show 2 Likes2
Actions
Peter Brinkhuis @ Hansjörg Wolff on May 1, 2020 5:56 PM
Mark Correct
Correct Answer
You don't need VS 2015, you can just use Visual Studio 2019 like I do. I think SolidWorks ships VS 2015 with it or something. It used to be VS 2005 or something old like that.

VBA and VB.net are built for non-programmers basically, that's why they need so many words for simple actions. I really don't like the VBA syntax, I haven't tried VB.net and I love C#.

You will find very little information on the web about the combination of C# and SolidWorks. But you don't really need to. All examples in the API help are specified for all three languages. I browse the API help every single day for SW questions and browse web for all kinds of C# questions but never needed to search C# questions related to SolidWorks.

SolidWorks code samples from 2008 will most likely still work. There might be new versions of a method that works better or has more parameters, but that's about it.
Like • Show 2 Likes2
Actions
Peter Brinkhuis @ Artem Taturevych on May 1, 2020 5:59 PM
Mark Correct
Correct Answer
Very helpful stuff. I still create VBA macros for exactly the same reason.
Like • Show 1 Like1
Actions
Hansjörg Wolff May 2, 2020 1:53 PM
Mark Correct
Correct Answer
Hello to all,
Funny thing, while i lay in the bett and sleep, here comes a lot of help for my project.
Today I have to met the decission what language i want to use.

The following hints helped at my decission.

1. The comparions table from Artem.

2.
VB.net since the syntax is nearly interchangable and you can generally copy VBA code into vb.net with only minor modifications to get started

3.
The goal is just more about having additional functionality over VBA.

4.
VBA and VB.net are built for non-programmers basically
(therefore for people like me :-)

5. The Visual Studio IDE is much more comfortable than the internal VBA in SWX.

6.
But C# is way more compact (I would spend about 10-20% less time to develop the same simple app).
Of Course an importend argument, but i am sure, i will do so much misstakes and delete and rewrite so much code, that the advantage of 20% will carry no wight in my case.

So VB.Net is my choise.

Lets start with the first exercise.

.... hours later....
i have my first succes, but the way was full of stones.
Like • Show 3 Likes3
Actions
Hansjörg Wolff May 3, 2020 8:48 AM
Mark Correct
Correct Answer
My stony road to first success....

The first exercise (the legendary "Hello World") was no Problem.
I can test with hello world if the debugger mode is working now.

The second exercise was to change "Hello World" to Hello SolidWorks followed with SWX Version number.
Therefore I need a connection from VB.net to SWX.
I try to followed the tutorial from Artem. But I did not find the right places in my macro to add the code from him.
This morning I tried again, and it works fine.
```
Module Module1
    Const Prog_ID As String = "SldWorks.Application"
    Sub Main()
        Dim progType = System.Type.GetTypeFromProgID(Prog_ID)
        Dim swApp = TryCast(System.Activator.CreateInstance(progType), SolidWorks.Interop.sldworks.SldWorks)
        swApp.Visible = True
        Dim Message As String
        Dim swVersion As Integer
        swVersion = swApp.DateCode
        Message = "hello SOLIDWORKS " & swVersion.ToString
        'show message
        MsgBox(Message)
    End Sub
End Module
```
My workaround yesterday was to try the way from the Luke Mallpass book.
(Page 39, 53 + 54)
After many unsuccessful attempt and lot of recycled Bits and Bytes. I found the solution.
```
Imports SldWorks

Module Module1

    Dim swApp As SldWorks.SldWorks

    Sub Main()
        swApp = GetObject("", "sldworks.application")
        Dim Message As String
        Dim swVersion As Integer
        swVersion = swApp.DateCode
        Message = "hello SOLIDWORKS " & swVersion.ToString
        'show message
        MsgBox(Message)
    End Sub

End Module
```
Both solution are working. The point I didn't understand.
At Artems way, I have to add only the reference Solidworks.Interop.sldworks by use the filesystem.
At Luke´s way I have to add the SWX Type Library, SWX Command type Library, SWX Constant type Library and SWX exposed type libraries. The adding was done as COM type library.
In the Code Sample on Page 54 he imports only the SWX Type Library

This morning I found a third solution for the references.
In the last posting of this thread you can read a mix out of adding as COM library and imported dll.
In this case the SWX Constant type library will double inserted?

What´s the difference of the way to add references? what´s the right way?
Like • Show 1 Like1
Actions
Casey Balderson @ Artem Taturevych on May 4, 2020 9:01 AM
Mark Correct
Correct Answer
Artem Taturevych wrote:
I believe you are talking about the Edit and Continue. You can use it in C# as well.
Artem Taturevich, you are correct, I was referring to Edit and Continue. I've been using C# (although only for about 6 months now), and all this time I thought it was strictly VB.NET that allowed for Edit & Continue. Thank you for clarifying, and thanks for correcting me.

Also, I agree with Amen Allah Jlili about CADSharp. I can attest that they provide a healthy jump start to accelerating your programming knowledge. And they are always available to help when you run into a problem. And they really are there to help build the programming community, in addition to this forum. they're a great tool to have in your pocket.

SolidWorks Academy videos are good. I personally struggle with the language curve being from the states, but I have gone back to them quite often with the help of CC and google translate. I also recomend the SolidWorks World videos as another free resource. They are packed with excellent information.

Another note for considering the future of coding. Microsoft tried to put a plan in place to ax VB.NET, as it's popularity is grossly trailing C#, among other languages. They seem to have changed their mind after It got a lot of push back from the dev community to continue evolution, but Microsoft landed on only continuing support, and it would no work to evolve the language (https://www.zdnet.com/article/microsoft-we-wont-evolve-visual-basic-programming-language-but-well-open-it-to-net-5/ ). Seems like we have bought more time for VB.NET support, but I don't think this will be Microsoft's last attempt to drop support for it. VBA is still around though, so who knows what the future entails.

However, I do agree with your decision to move forward with VB.NET. It will help you focus more on the API for now with minimal syntax adjustment, instead of trying to learn a whole new language and API at the same time. There's always converter.telerik.com/ if you change your mind.
Like • Show 1 Like1
Actions
Hansjörg Wolff @ Hansjörg Wolff on May 10, 2020 7:25 AM
Mark Correct
Correct Answer
1-KRUWE1 schrieb:
.... What´s the difference of the way to add references? what´s the right way?....
Read the answer of this question in this thread.
Or go direct to the link with the explaining from Artem.
Like • Show 0 Likes0
Actions
Hansjörg Wolff May 11, 2020 2:00 PM
Mark Correct
Correct Answer
Is it ok to post here all the solutions for the exercises in Mike Spens book in VB.net code?
Before I go on, I will ask Mike for permission.
Like • Show 0 Likes0
Actions
Mike Spens @ Hansjörg Wolff on May 11, 2020 4:26 PM
Mark Correct
Correct Answer
Thanks for sharing your experience so others can learn. In Automating SOLIDWORKS Using Macros, GetObject vs. CreateObject are described on pg. 148. Check the index for more detail on the two. Lots of info online as well.
Basically, GetObject connects to a running SOLIDWORKS session, and CreateObject launches a new instance. Artem Taturevich technique has "style". All of his code does. Either way, you're best served by adding references to the SOLIDWORKS type library and constants type library to simplify coding and make use of Intellisense. SolidWorks.Proxy.Solidworks is for macros. swpublished is for add-ins.

As far as sharing from the book, feel free to share what you've learned rather than full solutions.
Like • Show 3 Likes3
Actions
Hansjörg Wolff @ Mike Spens on May 16, 2020 7:53 AM
Mark Correct
Correct Answer
Hello Mike Spens
first of all thanks for your reply, and the OK to use your book.
I try to adapt your hint to the need references.

I understand, for macros I don't need the swpublished, but therefore the solidworks.Proxy.solidworks.
But I can not find something similar to solidworks.proxy.solidworks.
Not as COM Object and not as References for .NET Projects
Where can I find it?

One additional question.

1-1D8G3DY schrieb:
....GetObject connects to a running SOLIDWORKS session, and CreateObject launches a new instance.....
Is this a general hint, or is it a hint for a mistake in my code samples above?
I tried to change the code of my second sample.
```
        'swApp = GetObject("", "Sldworks.application")
        swApp = CreateObject("", "Sldworks.application.27.5.0")
```
But I only got a error message in the editor and no new SWX Instance.

What steps are additional needed to create a new instance?
Like • Show 0 Likes0
Actions
Mike Spens @ Hansjörg Wolff on May 18, 2020 12:58 PM
Mark Correct
Correct Answer
Hi Hansjorg,
This discussion probably deserves its own thread. However, there are quite a few with similar answers already in the forum.
Application.SldWorks or CreateObject("SldWorks.Application") ?
In answer to your earlier question, you should never need to manually add the Proxy library. It is for VSTA macros only.

Mike
Like • Show 2 Likes2
Actions

Hansjörg Wolff May 24, 2020 4:11 PM

With the hints from mike I start a new exercise.

For the next exercise I need additional the Modeldoc2 interface.

Presumably I add the name spaces as net Object an not as Com Objects. I need a different code than in the book.

Module Module1
    Const Prog_ID As String = "SldWorks.Application"
    Sub Main()
        Dim progType = System.Type.GetTypeFromProgID(Prog_ID)
        Dim swApp = TryCast(System.Activator.CreateInstance(progType), SolidWorks.Interop.sldworks.SldWorks)
        swApp.Visible = True
        Dim Message As String
        Dim swVersion As Integer

        'Dim swDoc As modeldoc2   '<- no IntelliSense support , and error message "modeldoc2 ist not defined
        'Dim swDoc = TryCast(System.Activator.CreateInstance(progType), SolidWorks.Interop.sldworks.ModelDoc2)  <- My trail and error solution :-\
        Dim swdoc As SolidWorks.Interop.sldworks.ModelDoc2 ' <-  solution suggested by help of Visual Studio
        Dim swtitle As String
        swdoc = swApp.ActiveDoc
        swtitle = swdoc.GetTitle

        swVersion = swApp.DateCode

        Message = "Hello SOLIDWORKS " & swVersion.ToString _
            & vbCrLf & "Active: " & swtitle

        'show message
        MsgBox(Message)
    End Sub
End Module

is my solution ok, or is there a better, or cleaner way?

Actions

Mike Spens @ Hansjörg Wolff on May 28, 2020 11:50 AM
Mark Correct
Correct Answer
Edited to correct the syntax. It will be much simpler to add Imports statements in your module. Visual Studio also suggests this as a solution.
```
Imports SolidWorks.Interop.sldworks
Module Module1
...
```
Review the description of using Imports on pg. 7 in the book, or the Microsoft documentation here...
Imports Statement - .NET Namespace and Type - Visual Basic | Microsoft Docs
Like • Show 0 Likes0
Actions
Hansjörg Wolff @ Mike Spens on May 27, 2020 5:03 PM
Mark Correct
Correct Answer
Ok I think I did test this solution also, but it doesn´t work. Maybe I added the imports statements at the wrong position.
I tried again, and now it works, but I have to add the imports statement above the row with the modul entries.
If I add the statement below of the row with the module entries, the command is underlined with a red line.

My insights from today and the last days:
1. On Errors use the help of Visual Studio. The hints of the support window are very helpful.
2. Read the chapter "API Help" beginning on page 15 up to page 21 really attentively. After reading this chapter I understood much more of the code from the macros I copied from the web.
3. switch off the web help for SWX API Commands. Use the local help as recommended in the book.
4. be careful! Programming is like a drug :-)
Like • Show 0 Likes0
Actions
Hansjörg Wolff Jun 8, 2020 12:59 PM
Mark Correct
Correct Answer
Yesterday I had a little problem.
In the exercise a variable should declared to use with the Windows Combobox without adding the necessary referenced.
I try to wrote code exactly like in the book, but the intellisense always edit my code.
After a while I found a working solution. See my Solution in the code below.
```
 'Dim MyCombo As Windows.Forms.ComboBox  <- Code as writen in the book
  Dim MyCombo As System.Windows.Forms.ComboBox  ' <- My Solution
```
Is the change necessary because of the ussage of VB.net instead VSTA, or is it a misstake in the exsample in the book?
Like • Show 0 Likes0
Actions
Mike Spens @ Hansjörg Wolff on Jun 8, 2020 7:28 PM
Mark Correct
Correct Answer
VSTA always adds the "Imports System" line with the rest of the Imports at the top of the macro code, so it isn't explicitly mentioned in the book. Hopefully you are beginning to understand how Namespaces (libraries) are declared globally (Imports) versus at the time of use like your example.
'Dim MyCombo As Windows.Forms.ComboBox <- Code as writen in the book Dim MyCombo As System.Windows.Forms.ComboBox ' <- My Solution
Like • Show 1 Like1
Actions

Incoming Links

Re: Where to start? Programming for SWX + PDM.

Time to learn programming. -> strengthened from the crisis

Outcomes

Related Content

Recommended Content

Incoming Links