LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Auto generated application config file name

Hello,

I am using LabVIEW 2016, 64 bit version.  I have built an application and associated installer with a destination folder (installer specification) of "Example Application Two."  The application is named "Example Application."

 

After installing and running the application, the auto generated application configuration file is "Example Application Two.ini."  I have specified to "Use custom configuration file" in the application build spec.  The name of the specified configuration file is "Example Application.ini."

 

Has anyone seen similar behavior?  It appears that specifying a "custom configuration file" in the application build spec does not persist when building into an installer.

 

I would like to be able to have my application auto generate a configuration file that shares the same name as the application rather than the folder that the application is in.  Any thoughts on how to do this?

 

Thanks in advance,

Brooks

0 Kudos
Message 1 of 4
(2,409 Views)

Please disregard this post.  I found the problem.

 

Thanks,

Brooks

0 Kudos
Message 2 of 4
(2,400 Views)

State what you found!

 

Others reading this post, maybe someone in the future searching for the same problem will learn from your newfound wisdom.

0 Kudos
Message 3 of 4
(2,339 Views)

There was a VI, that I was not aware of, that was causing this behavior.

 

Brooks

0 Kudos
Message 4 of 4
(2,279 Views)