When does the ActiveX Server CLSID change?

[amandion]

Hello,

We have a large application for Windows that we compile to an EXE. We enable the ActiveX server option in our build spec so that clients can programtically use our Application as an API via ActiveX. We've noticed that programs we've written to use the ActiveX server will crash after new builds of our LabVIEW application because the CLSID of the ActiveX server will change.

Is there a way to keep the CLSID the same after each build of a LabVIEW application? If not, is there at least a way to predict when the CLSID wil change?

[Johnnyg17]

It seems there is not currently a way to keep a static CLSID for your ActiveX project as it looks like LabVIEW re-registers a COM application with each build it undergoes (and thereby creating a new CLSID each time). I do not know of a way to predict what the CLSID is after each build but it is currently an issue that someone has found a work around for (as well as bringing it up on the Idea Exchange): http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Project-Setting-defines-fixed-CLSID-for-ActiveX-Inter-...

[MaxEngee]

We have the same problem.

I noticed that the ID does not change if you change only build version.

I'm looking for a solution for a long time.