{"id":5692,"date":"2014-06-11T00:58:48","date_gmt":"2014-06-11T07:58:48","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Solid-Edge-Blog\/First-Steps-to-Automation-Part-2\/ba-p\/32496"},"modified":"2026-03-26T07:30:34","modified_gmt":"2026-03-26T11:30:34","slug":"first-steps-to-automation-part-2","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/solidedge\/first-steps-to-automation-part-2\/","title":{"rendered":"First Steps to Automation – Part 2"},"content":{"rendered":"

…continued from Part 1<\/A><\/P>
\n


Keep typing more lines as shown below:<\/P><\/p>\n

\"08.png\"<\/span><\/P>
\n


As evident, oDoc<\/FONT> stores the Draft Document whose type definition comes from the DraftDocument type library referenced earlier.<\/P><\/p>\n

Similarly, oSel is a variable that stores the object of type SelectSet. Though we are using the selection set in the draft document alone, selection set exist in other environment like Part and Assembly too. Hence it comes from the SolidEdgeFramework type library which hosts definitions for objects common to various Solid Edge environments.<\/P><\/p>\n

The SolidEdgeFramework.<\/FONT> prefixed to the SelectSet<\/FONT> means the later is fully defined and leaves no ambiguity to VB.Net. The prefix is also called a qualifier.

\"09.png\"<\/span>Note: <\/STRONG>As you type, some lists and tooltips will appear automatically. This is the Intellisense<\/EM> feature of Visual Studio. Ignore them for the time being and continue typing. Your code should now appear as below:<\/P><\/p>\n

\"10.png\"<\/span><\/P>
\n


Notice there are no scary formulas or number crunching so far.<\/P>
\n

Solid Edge automation using programming is fun !! \"Cat<\/P>
\n

Note:<\/STRONG> Solid Edge automation using Excel is fun too – refer this article<\/A> and this one<\/A>.<\/P>
\n


Now it’s time to access objects and store their values in the variables.
Add more lines after the line Dim<\/FONT> iCount<\/FONT> As Integer<\/FONT> and before the End Sub<\/FONT> line:<\/P><\/p>\n

\"11.png\"<\/span><\/P>
\n


\u2022<\/STRONG> oApp<\/FONT> stores the Solid Edge object.
\u2022<\/STRONG> Marshal <\/FONT>comes from the namespace added at the very top of the code window that begins with Imports<\/FONT>…
\u2022<\/STRONG> Marshal <\/FONT>has a method called GetActiveObject<\/FONT> which uses the ProgID or Program ID of Solid Edge which is “SolidEdge.Application”<\/FONT> and stored in the registry.<\/P><\/p>\n

At your own risk, you can search for SolidEdge.Application<\/FONT> in the Windows registry. To open the Windows Registry, press Win+R and type regedit. Associated with the Prog ID is the full path and name of the Solid Edge program i.e. Edge.exe found in the LocalServer32 node just above the Prog ID in the registry.<\/P><\/p>\n

Similar to GetActiveObject<\/FONT> is CreateObject<\/FONT> <\/STRONG>which also takes the ProgID SolidEdge.Application<\/FONT> and launches or starts Solid Edge through VB.Net. You can use CreateObject<\/FONT> in a macro meant to be used from a desktop shortcut and not from a button inside Solid Edge.<\/P><\/p>\n

When using CreateObject<\/FONT>, additionally the Visible<\/FONT> property of Solid Edge needs to be set to True <\/FONT>as below:<\/P><\/p>\n

\"12.png\"<\/span><\/P><\/p>\n

Notes:<\/STRONG><\/P>
\n

\u2022<\/STRONG> CreateObject does not require Marshal <\/FONT>or the Imports <\/FONT>statement at the top of the program.<\/P>
\n

\u2022<\/STRONG> Don’t use CreateObject<\/FONT> in the SelCount macro.<\/P>
\n


Solid Edge must be running to use the SelCount macro. To check this,<\/P>
\n

\u2022<\/STRONG> Start the Windows Task Manager by right clicking the task bar and selecting this option.
\u2022<\/STRONG> Take the processes tab and Edge.exe should be listed with a description Solid Edge.<\/P><\/p>\n

Back to the code,
\u2022<\/STRONG> On the next line, oDoc<\/FONT> stores the ActiveDocument<\/FONT> property of oApp<\/FONT> which is none other than Solid Edge itself.
\u2022<\/STRONG> oApp<\/FONT> knows which is the currently active document and assigns it to oDoc<\/FONT>.
Chances are no document is open in Solid Edge so the ActiveDocument<\/FONT> property would be blank and the program might run into an error condition.
This will not happen if you run this macro from a button on the ribbon bar in the draft environment, so a draft document will always be available.

\u2022<\/STRONG> oSel<\/FONT> stores the SelectSet<\/FONT> which is the set of selected objects in the active draft document via oDoc.SelectSet<\/FONT>

\u2022<\/STRONG> Finally, iCount<\/FONT> stores the number or count of selected objects.<\/P>
\n


Your code should now appear like this:

\"13.png\"<\/span>

The last step is to actually display the count in the Status bar or PromptBar of Solid Edge.
For this, manipulate the StatusBar<\/FONT> property of oApp<\/FONT> i.e. Solid Edge as below:<\/P>
\n


oApp.StatusBar = iCount.ToString() + ” object(s) selected.”<\/FONT><\/FONT>

The + sign adds up two strings:
1. The number iCount<\/FONT> converted to string by suffixing to it the ToString()<\/FONT> function, and
2. The string “object(s) selected.”<\/FONT>.<\/P><\/p>\n

The completed program should appear as below:<\/P><\/p>\n

\"15.png\"<\/span><\/P><\/p>\n

This displays a nice message in the status bar, for e.g.<\/P><\/p>\n

\"14.png\"<\/span><\/P><\/p>\n

Its time to convert the code into an executable macro. This process is called Build.<\/P>
\n


In Visual Studio 2010 Express if you don’t see the Build Menu.
1. Click on Tools menu.
2. Click on Settings.
3. Click on Expert Settings.
4. Click on Tools Menu, Select Options. In the dialog box, check the Show All Settings option in the bottom left.
5. In the above dialog, now choose Projects and Solutions. Expand General. Check the option Show advanced build configurations. Click Okay.

From the menus, select Build > Build Solution.
Read the status bar in Visual Studio which should read ‘Build started…’ then ‘Build succeeded’.

Go back again to Window Explorer and check the Debug folder. You should now see SelCount.exe<\/P><\/p>\n

\"16.png\"<\/span>This is our macro, ready for use in Solid Edge. The exe file does not have an icon. You can use the SelCount.png file attached with this blog post and copy it to the debug folder as shown in the image besides.<\/P>
\n


alternatively you can use MS Paint to create a 32×32 PNG, BMP or ICO file and name it same as that of the macro i.e. SelCount.<\/P>
\n


To assign the macro to a button on the ribbon bar in the Draft environment, follow these steps:<\/P>
\n

1. Right-click on an existing button on the ribbon to display the context menu.<\/P>
\n

2. Select Customize the R<\/U>ibbon from the menu.<\/P>
\n

3. In the Customize dialog, the Ribbon tab should be active.<\/P>
\n

4. On the TreeView on the right side, expand the Home or Sketching nodes – both have the Select group.<\/P>
\n

5. Expand the Select node and also select it.<\/P>
\n

6. At the top on the left side, pull down the list called Choose com<\/U>mands from:<\/P><\/p>\n

\"17.png\"<\/span><\/P><\/p>\n

7. At the bottom side of the dialog, click B<\/U>rowse…<\/P>
\n

8. Pick the SelCount.exe<\/P>
\n

9. Pick the Selcount.exe again in the left-side list in the Customize dialog.<\/P>
\n

10. Click A<\/U>dd >><\/P><\/p>\n

\"18.png\"<\/span><\/P><\/p>\n

11. If you have also copied the SelCount.PNG to the same folder as the EXE, the icon will be picked up automatically and displayed.<\/P>
\n

Note:<\/STRONG> If you want your own icon, make a 32 x 32 PNG file using MS Paint. ICO and BMP files should also work.<\/P>
\n

12. Right-click the SelCount.exe and select Rename or simply press F2 to rename it.<\/P>
\n

13. Select the SelCount node in the tree and click Move Down several times to move it to the end of the list which also moves it appropriately in the ribbon group.<\/P>
\n

14. Right-click on the SelCount node in the tree and select Small\/Large button and Text\/No text as desired.<\/P>
\n

15. To assign a keyboard shortcut, take the Keyboard tab and follow the steps in the image below.<\/P><\/p>\n

\"19.png\"<\/span><\/P><\/p>\n

16. Close the Customize dialog. Hover the mouse cursor over the SelCount macro in the Sketching tab on the ribbon.<\/P><\/p>\n

\"20.png\"<\/span><\/P>
\n

17. Check everything appears fine and the macro works properly.<\/P><\/p>\n

Even with no object selected, the PromptBar should display<\/P>
\n

‘0 object(s) selected’.<\/FONT><\/P><\/p>\n

See the attachments with this post below for the SelCount.PNG file.<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"

…continued from Part 1
\n Keep typing more lines as shown below: <\/p>\n

As evident, oDoc stores the Draft Document whose type definition comes from the DraftDocument type library refe…<\/p>\n","protected":false},"author":42979,"featured_media":5732,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1,96],"tags":[33],"industry":[],"product":[],"coauthors":[],"class_list":["post-5692","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","category-tips-tricks","tag-developer"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/8\/2019\/09\/20-7.png","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/posts\/5692","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/users\/42979"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/comments?post=5692"}],"version-history":[{"count":14,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/posts\/5692\/revisions"}],"predecessor-version":[{"id":5733,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/posts\/5692\/revisions\/5733"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/media\/5732"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/media?parent=5692"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/categories?post=5692"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/tags?post=5692"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/industry?post=5692"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/product?post=5692"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/solidedge\/wp-json\/wp\/v2\/coauthors?post=5692"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}