SE ST3 - Where to find CATID's for sync environments



I've been looking for the CATID's of the Solid Edge Synchronous environments. They aren't included in the secatids.h file.


I found a post here in the forum where the catids are listed, thank you verry much.


Also I found the following in the VB.Net Addin example of Solid Edge.

Module SolidEdge

    ' Define constants for various edge environments commonly used by add-ins. More

    ' GUIDs exist in the edge\sdk\include\secatids.h file.

    Public Const CATID_SolidEdgeAddIn As String = "{26B1D2D1-2B03-11d2-B589-080036E8B802}"

    Public Const CATID_SEApplication As String = "{26618394-09D6-11d1-BA07-080036230602}"

    Public Const CATID_SEPart As String = "{26618396-09D6-11d1-BA07-080036230602}"

    Public Const CATID_SESyncPart As String = "{D9B0BB85-3A6C-4086-A0BB-88A1AAD57A58}"

    Public Const CATID_SEAssembly As String = "{26618395-09D6-11d1-BA07-080036230602}"

    Public Const CATID_SESyncAssembly As String = "{2C3C2A72-3A4A-471d-98B5-E3A8CFA4A2BF}"

    Public Const CATID_SESheetMetal As String = "{26618398-09D6-11D1-BA07-080036230602}"

    Public Const CATID_SESyncSheetMetal As String = "{9CBF2809-FF80-4dbc-98F2-B82DABF3530F}"

    Public Const CATID_SEDraft As String = "{08244193-B78D-11D2-9216-00C04F79BE98}"

    Public Const CATID_SEWeldment As String = "{7313526A-276F-11D4-B64E-00C04F79B2BF}"

End Module


OK, I added the definitions to the secatids.h and this works for me.



But I'm curious where these ids come from. I've been looking for them in the registry but I haven't found them, expect in the registry branch of my addin :-(


Can one of you tell me how and where the ids can be found/detected ?


- Thomas



Posted by: Thomas Juhlke
Post date: 4/5/2011 1:48:58 AM


RE: SE ST3 - Where to find CATID's for sync environments



The SDK Help is much more useful than it used to be. On the welcome page of the help, there is a link to information discussing the status of Sync in ST3. In short, Sync API's have been deprecated in ST3 and moving forward. Like I said, read the SDK help for details. Also, you should never modify a 3rd party's header file. If they were there but now are not, then they have been removed for a reason. If you really need the GUID's, define them in your own .h file. Where do the GUID's come from? Solid Edge development generates the GUID's when the need arises. The official declarations will always be found in secatids.h and not necessarily somewhere like the registry.


Posted by: Jason Newell
Post date: 4/6/2011 11:04:00 AM

RE: SE ST3 - Where to find CATID's for sync environments



thank you for your reply.

I found the GUID's in \SDK\Samples\Addins\VB .NET\SEAddIn\SEAddIn\SolidEdge.vb


As far as I knew it from former SolidEdge Versions you need the environment id's to make an addin available in the individual Solid Edge environments.

If you define a new part in ST3 you can change via "transition to ordered" and "transition to synchronous" the working environment. If I want to write an addin which is available in both environments, I thought I'll need the GUID's of the individual environments. Isn't it?


- Thomas


Posted by: Thomas Juhlke
Post date: 4/12/2011 12:57:36 AM

RE: SE ST3 - Where to find CATID's for sync environments

The GUID's are listed in the VB file because you don't can't use C++ header files (.h) in languages like VB. You must redeclare them in the other languages.


To answer the Traditional vs Synchronous, In ST & ST2 you did have separate environments. In ST3, they have deprecated the Synchronous API and merged the Synchronous environment into the Traditional environment. This is covered in the ST3 SDK Help. If you have not read the ST3 SDK Help, I encourage you to do so as there is quite a bit of information regarding the change. Technically speaking, the Synchronous API's still exist in ST3 but will be removed in ST4.


Posted by: Jason Newell
Post date: 4/12/2011 9:09:04 AM

RE: SE ST3 - Where to find CATID's for sync environments

The synchronous environments did not go away in ST3. An add-in must still register for the environments if an add-in wants a chance to add UI to the environments


Posted by: R.D. Holland
Post date: 6/20/2011 6:45:03 AM