10-09-2007 05:06 AM
10-09-2007 08:12 AM
10-11-2007 03:48 AM
Hi Antonio Lie
Thank you for the reply. I followed the same procedure as you have suggested
but i am stuck up with another issue, i am not able to specify the destination directory
where my dll needs to be installed.In the option "Default Installation Base Directory"
there is no option to specify the Directory where i need to install
Could you please let me know.
Regards
rags
10-11-2007 08:30 AM
rags,
What is your default installation base directory?
You can select the windows volume directory and specify the rest of the path as the default Installation subdirectory.
The default installation base directory can be modified while executing the installer (if you do not check the 'Do Not ask User for Installation Directory' box)
Regards.
Antonio.
10-12-2007 03:46 AM
10-12-2007 07:54 AM
Rags,
What INI file are you talking about?
Could you be more explicit?
Regards.
10-14-2007 11:36 PM
Hi Antonio.
Basically the objective of the installer is:
job 1: copy 2 dll's into specified folder(which we have done)
job 2: appened or modify, a configuration file if existing, else copy the configuration file in the specified folder
these are the two things, that the installer needs to do.
for job 2 , i have written a code in labview.
while creating the installer i want to call both job 1 and job 2.
At the end when i run my setup created by i want to acheive Job1 & 2.
i hope you have a idea of what i need to do
regards
rags
10-15-2007 08:26 AM - edited 10-15-2007 08:26 AM
rags,
In order to accomplish job 2 you can use a custom command.
1. In the deployment utility dialog go tho the Installer Options tab
2. Click on the 'Custom Commands' button
3. Add a new command
4. Select 'Installer Executable Directory' as the command directory
5. Add the name of your exe (the exec reated in LabVIEW) in the 'command and argument' box.
6. Build the installer.
7. Once you build it, copy your exe to the installer folder (same directory where setup.exe is located).
8. The custom command will be executed as part of the installer execution.
Hope it helps.
Message Edited by Antonio Lie (NI) on 10-15-2007 08:30 AM