LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
DrST

Project Setting defines fixed CLSID (for ActiveX Inter Process Communication, e.g. Teststand uses a vi to cummincate with build application)

Status: Declined

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined. 

I am using ActiveXServer property of build LabView apllications to realize Inter Process Communication.

Unfortuneately the CLSID (a unique identifier that allows each aplication to register to the ActiveX registered service on Operating System level) will be changed every time the project setting are changing (e.g. if a new file will be added to aplication).

 

The official workaround from NI support is to copy once the CLSID properties out of the project file (see attachment, lvproj has to be opdened with an editor, e.g. NotePad++) and to reuse these initial CLSID properties after every change to the project. This means you have to e.g. add source file, save and close lvproj, open in editor, replace all proerties with initial ones, close lvproj, open lvproj in labview, build your application.

Of course this workaroung works but makes no fun and is a bit a shame...

 

So my idea is to get an additional Option in "Advanced" section, nearby "Enable ActiveX server" setting, to define a fixed CLSID.

 

Unbenannt.PNG

 

For all interested people a bit more background why this is causing trouble:

Imagine you have to write automated software with labview and teststand for an testbench... If you e.g. have 10 vi's used by Teststand to cummnicate to an application (you will use an application because you like to save your code from operator changes or because it makes it much easier to distribute your application to several testbenches). Every time you make changes to your application, rebuild it and distribute it, the teststand used vi's will have a problem to find the registered service because the rebuild application uses now an different ID which will not automatically recognized by your vi's. So you have to open all of your 10 vi's and have to link these to the new service. Afterwards you have to distribute these vi's too.

 

3 Comments
MaxEngee
Member

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.

MaxEngee
Member
Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.