I have what hopefully may be a quick question.

I am repackaging WinSCP. I do not want to entirely overwrite an .ini file in "Program Files\Winscp\winscp.ini" that has user configurations (in case they are updating from a previous version). I do want to overwrite certain values in the .ini file itself (as insurance that the user did not somehow reenable updates). However, if there is no .ini file I want to put in my default .ini file.

Is there an easy way to accomplish this?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I don't know which authoring tool you use, but the one I have here (Installshield Adminstudio 2010), when defining INI file changes, it allows me to specify a 'do not overwrite' setting for the key values.

Had a quick look at the IniFile table and the relevant entry had a 1 in the Action column. You can find more info on that table here

PJ
Answered 09/30/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
I do have adminstudio as well (an older version) and I did have things set up that way. In the file and folders view I did not copy my default .ini file into the WinSCP directory... and when upgrading that worked perfectly as the .ini file was there from the old version. However, when doing a fresh install of WinSCP 4.2.9 just the .ini table did not seem to create an actual .ini file (Should it?). When I ran WinSCP for the first time it created its own .ini file, not using what was defined in the .ini file table.
Answered 10/01/2010 by: deranjer
Senior Yellow Belt

Please log in to comment
0
Whoops... nevermind, operator error, it does create the ini file from the .ini table.... as long as you don't specify the wrong directory to put it in....
Answered 10/01/2010 by: deranjer
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity