I have a software that relies on an ini file for the serial number and another code for activation. I imported the ini file in Wise Package Studio 7 (SP3) and I took a look at the ini file and the order was all messed up. The serial number has to appear first in the ini file and then the other activation code. I tried to delete the information and add the lines one by one with Orca. Once I save the transform and open it again, everything is messed up in the table. Of course, when I install that package, the lines in the ini file are not in the order they should be and the activation fails.

I'm using the inifile table instead of a normal file because I want to be able to use a property for the serial number and another property for the other activation code.

Am I doing this the right way? Can I get Windows Installer to write the ini file the way I want it to be written?

Thank you.
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
read up on INI file standards. I do not know whether order is part of that.
But you could look in the INIfile table in Wise and maybe re-order the lines. But shouldn't the activation code look for the section and value of the SN and activation code, not rely on one or the other to be listed first?
Answered 08/04/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
You are absolutely correct. The error was on me, not on the software.

Thank you...
Answered 08/04/2009 by: sylvain_langlois
Orange Belt

Please log in to comment
0
Remember also that some vendors uses files with an INI extension but which aren't in INI format. I suspect that's the case here. Wise can be pretty dumb in handling these. In practice, unless I need to use properties to populate an INI's content, I always select 'Treat as File' when capturing.
Answered 08/05/2009 by: VBScab
Red Belt

Please log in to comment
0
I concur with VBScab - in fact I usually go one step further and always use the "Treat As File" option on all INIs.
If I want to update properties then I can always set the MSI to just punch that line into the file.
Answered 08/18/2009 by: JillBA
Senior Yellow Belt

Please log in to comment
0
I agree. Treat as file for the win. Cleaning up a vendor's 2000 line INI file when every other line starts with a colon is not my idea of fun.
Answered 08/18/2009 by: elgwhoppo
Senior Purple Belt

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