/build/static/layout/Breadcrumb_cap_w.png

Ini file Problems

Hi,

I am quite new to packaging, so forgive me if this question seems obvious.

I have created a .msi to install a local application, which works fine, However i have also set the msi to remove any older version of this app, if detected.

My problem resides with the application's .ini file. If I install the app without any previous version, the .ini file is installed correctly, without any problems.

If I install the app, but get it to remove a previous version, the .ini file is not updated correctly.

The applications Original .ini file looks like this:

--------------------------------------------------------------------------------------------
[XCS Access]
LastEnvironment=1
Environment1=Training,server1,9361
[Login]
Username=
--------------------------------------------------------------------------------------------
The new .ini file should look like this:

--------------------------------------------------------------------------------------------
[Login]
Username=joanne
[XCS Access]
Environment1=(Training),server1,1111
Environment2=(Live),server1,1112
LastEnvironment=1
[Install]
RemoteInstallationDirectory=\\server1\app1
--------------------------------------------------------------------------------------------

But what I get is this:

--------------------------------------------------------------------------------------------
[XCS Access]
Environment2=(Live),server1,1112
[Install]
RemoteInstallationDirectory=\\server1\app1
--------------------------------------------------------------------------------------------

My msi's inifile table looks like this, please excuse the bad formatting. I have tried the different 'Action' types as well.

Filename, Inifile, DirProperty, Section, Key, Value, Action, Component_
"ecamis.ini","Environment1","WindowsFolder","XCS Access","Environment1","(Training),server1,1111","0","IniFile"
"ecamis.ini","Environment2","WindowsFolder","XCS Access","Environment2","(Live),server1,1112", "0","IniFile"
"ecamis.ini","LastEnvironment","WindowsFolder","XCS Access","LastEnvironment","1", "0","IniFile"
"ecamis.ini","RemoteInstallationDirectory","WindowsFolder","Install","RemoteInstallationDirectory","\\server1\app1","0","IniFile"
"ecamis.ini","Username","WindowsFolder","Login","Username","joanne", "0","IniFile"



Any help would be gratefully recevied.




0 Comments   [ + ] Show comments

Answers (3)

Posted by: michaelnowell 16 years ago
Second Degree Blue Belt
0
Is the custom action 'RemoveExistingProducts' situated towards the end of the Execute Immediate sequence. I'm guessing that your new version is installing itself and then removing the previous apps ini values towards the end of the install.
Posted by: beefy66 16 years ago
Orange Belt
0
Thanks, you are exactly right. During the install I had noticed the the previous version was always being removed last. When I checked my InstllExecuteSequence table, RemoveExistingProducts was the very last action to be ran. Once I changed it to between the InstallValidate and InstallInitialize actions, the previous version was removed first and the .ini file was successfully replaced as I wanted.

Thanks for your help.
Posted by: michaelnowell 16 years ago
Second Degree Blue Belt
0
no prolem
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ