LV7.1 installer replaces .ini file

[Mads]

After upgrading to LV7.1 it seems impossible to get away from usig the application builder's installer (if you want support for analysis VIs), terrible enough, however the installer seems to replace the .ini file I include as well. If I distribute hello.exe I normally include a hello.ini file with a number of keys in it (hiderootwindow e.g.), however the LV installer seems to create it's own hello.ini which only contains the application section ([hello]) and nothing else. There must be a way to avoid this.

[Dr._Imad]

Hello,

I just used the application builder of version 7.1 and created an application. I included my application.ini file as a support file during the build process.

Then I installed the application.
The .ini file was not replaced by LabView.
It is still the same behavior as in previous versions of LabView.

If I rename my .ini file, and run the executable, LabView does create a new .ini file.
I assume your executable and .ini files have the same name (without the extension)! don't they?

[Mads]

Perhaps that's the problem; I did not add it as a support file in the build of the app, but as a file in the files section of the installer setup (should still work, but maybe there is a minor bug there...).

Mads

[m3nth]

This is definitely an issue--I had the exact same problem. Adding the file to the files section of the installer setup does not perform the same function as adding it as a support file and subsequently editing the destination in the files section of the installer setup.

Note that the files section of the installer setup looks identical for both of the operations above, but the expected outcome only results from adding the support file--not good from a user interface perspective.