When Building an Application, which .icd file gets used on the deployment machine?

[ColeVV]

Hello all,

I am building an application that needs to support multiple configurations for multiple cameras. I currently have a development machine with everything you would expect to be installed, and a deployment machine that does not have LabVIEW installed, but does have LabVIEW run-time, appropriate drivers and MAX.

My question is: When I build an application, I would like to be able to give a particular end user their own .icd file which the built application will recognize on their own machine. Then the .icd parameters can be tailored to their application. Is this possible?

I had hoped that this would just be the case, however when I compiled an application and tried to run it on the deployment machine it was obvious that the built application retained the .icd settings on the development machine and ignored the .icd settings on the deployment machine. Perhaps it has something to do with how I am compiling? Any additional info would be awesome.

Thanks everyone for your time!

[LVbum42]

Cole,

The easiest thing to do would be to manually replace the default .icd files with your configured .icd files at the directories specified in the following knowledge base.

Where Do I Place My Camera File Once I Download It?

LabVIEW won't copy the .icd configuration automatically because it is a configuration file for the IMAQ driver which is platform independent.  Another option would be to create VI that runs at installation or application run time that programmatically configures the .icd file.  You can add the .icd file to your project and copy the attributes to the camera file that exists on the deployed machine or replace it entirely.