/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi all

It's been one month and i am working with windows Installer in order to make an installation package for my software.

I am trying to get some configuration data frm user during installation and write them into a .ini file.

Not all data are written into the .ini file.

What i have already done is :
is made a Top dialog Graphic with text fields, each is associated with a property i have already created.
later on i write in the ini file settings the following lines:
[CGI Interface]
HTTP Port=[CGI]
[CSP interface]
Telephony System IP=[system]
CSP IP=[CSP]

after compilation ad installation, Telephony System IP is always empty eventhough user enters a value for it during installation.
So where is the problem.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
ORIGINAL: daher

Hi all

It's been one month and i am working with windows Installer in order to make an installation package for my software.

I am trying to get some configuration data frm user during installation and write them into a .ini file.

Not all data are written into the .ini file.

What i have already done is :
is made a Top dialog Graphic with text fields, each is associated with a property i have already created.
later on i write in the ini file settings the following lines:
[CGI Interface]
HTTP Port=[CGI]
[CSP interface]
Telephony System IP=[system]
CSP IP=[CSP]

after compilation ad installation, Telephony System IP is always empty eventhough user enters a value for it during installation.
So where is the problem.



I notice that you specified the property for Telephony System IP in lowercase, whereas all your other properties are in uppercase. Perhaps it might be worth a try using

Telephony System IP=[SYSTEM]

As an aside, personally I would have chosen a different property name than "system" ... there's always the potential for this property to clash with a directory property in the Directory table.

How about using (say) [TSIPADDRESS] as your property, and see if that works ?

Regards,

Spartacus
Answered 06/27/2008 by: spartacus
Black Belt

Please log in to comment
0
Well i have tried another property name such as "Daher"
but still i get the same empty result.
Note tat i did compile the program several times...Could it be related to this thing?
Answered 06/27/2008 by: daher
Orange Belt

Please log in to comment
0
Do you initialize this property in the Property Table ? If so, is it in uppercase in that table ?

In your dialog, are you making sure the property is also in uppercase ?

Finally, in your INIFile table, is the property in uppercase as well ?

Regards,

Spartacus
Answered 06/27/2008 by: spartacus
Black Belt

Please log in to comment
0
Well i can not see the property in the property table since when i created it i gave it no value so it is not saved.

the reason i did nt write any value is that i don't want tha the user sees these values during installation.

I will try again with givin initial values and apply the steps u mentioned then i 'll give my feedback

Thanks for the help
Answered 06/27/2008 by: daher
Orange Belt

Please log in to comment
0
Well i tried again:

i checked if the property name in bothe INItable and PropertyTable and Dialog do match
Beside that in the PropertyTable the property value is initialized to 1 and that appears during the installation...but if i change it in the dialog then i do not see the changes in the INI file.

by the way i am confroting the same problem whil updating xml files.

i could upload the log and exe, msi files but i don't have enough priviliges
Answered 06/27/2008 by: daher
Orange Belt

Please log in to comment
0
well right now it's working.

What i did is the following:

in INI file i had only one section name
before that i had also for every entry a section name
beside that i initialized all the created properties eventhough it does not look beautiful for a user

I hope sch an approach remains stable.

Best Regards
Answered 06/27/2008 by: daher
Orange Belt

Please log in to comment