LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

don't erase file when updating

My vi needs a config.ini which can be modified by users. And when they try to install new version of my app, this file is erased and replaced by the one in setup configuration (support file).
How can avoid this and keep the 'user-modified' config.ini ?

Thanx
Matt
(LV 6.1)
0 Kudos
Message 1 of 3
(2,590 Views)
Hi,
If you are facing such a problem then you must not be putting the ini file as a support file in your excutable but you must be creating it on run time when your program runs,if a file is already found there it must not create the file but must be using the old one,all this has to be controlled in your code.
0 Kudos
Message 2 of 3
(2,589 Views)
Hello,

Because the LabVIEW 6.1 Application Builder generates Microsoft Installer (MSI) installers, it must use the MSI rules for overwriting a file. These rules involve the following properties, which MSI installers evaluate from the top down.
Version
Date
Language

The answer of Vicky is one way to avoid your problem.
An other way would be to install a support file with an other name. Your program could then choose to use the config.ini file if one already exists or to change the name of the support file to config.ini in the other case.

regards

Marc Larue
Application Engineer
NIF
0 Kudos
Message 3 of 3
(2,589 Views)