Wednesday, 12 December 2012
Application Packaging Online Training - January 2013 Batch
Inviting registrations for Application Packaging Online Training batch for the month of January 2013.
Sunday, 4 November 2012
Application Packaging Online Training - November 2012 Batch
Inviting registrations for new batch of Application Packaging Online Training using AdminStudio, demo session scheduled on 7th November 2012.
What you need to attend training:
1. Laptop/Desktop with good Internet Speed
2. Headset in working condition both microphone, speaker
Demo Session Timings:
India: 10.30pm IST 7th November
USA: 12:00 Noon Eastern Time(EST), 7th November
UK: 5pm BST, 7th November
Interested candidates can reply me for registration and to know more about timings and fee details.
For candidates who are interested but unable to make it to above mentioned, please let me know and I can arrange another demo session in your flexible timings.
For more details of our training and consulting services, please visit www.apprepack.in
Tuesday, 7 August 2012
Application Packaging Online Training - August 2012 Batch- Weekend
New batch of Application Packaging Online Training starting from 25th August 2012
This is a weekend batch with 2 to 3 hours a day during saturdays and sundays. Anyone interested?, please contact me on Virtual.App.Packager@gmail.com
visit www.apprepack.in for more information on training topics.
Monday, 6 August 2012
MSI Kill Process - Installshield 2012 Spring
Installshield has introduced new feature in Installshield 2012 Spring edition, A inbuilt custom action which can terminate/kill process.
In Installation Designer -> Behavior and Logic -> CustomActions and Sequences, Right Click and select "New Kill Process"
-> If you are trying to terminate process using name choose FuncatioName as KillProcess or else choose KillProcessByID
-> Choose when you want to run the action and provide condition to run when satisfied.
-> If In-Script Execution is selected as one of Execute Immediate process. Goto Properties and create a New Property with Name ISTerminateProcesses and provide the list of process to be terminated.
-> If In-Script exeuction is selected as one of the deferred execution then create a property whose name is same as the name of the custom action ( in this example: KillWord ) give and provide the list of process to be terminated.
In Installation Designer -> Behavior and Logic -> CustomActions and Sequences, Right Click and select "New Kill Process"
Provide the name of custom action and then choose FunctionName, In-Script options
-> Choose when you want to run the action and provide condition to run when satisfied.
-> If In-Script Execution is selected as one of Execute Immediate process. Goto Properties and create a New Property with Name ISTerminateProcesses and provide the list of process to be terminated.
-> If In-Script exeuction is selected as one of the deferred execution then create a property whose name is same as the name of the custom action ( in this example: KillWord ) give and provide the list of process to be terminated.
Uninstall MSI using WiseScript
Following script checks for Veritas Netbackup Client if it is installed on the machine,
If exists, app will be uninstalled.
If exists, app will be uninstalled.
Create Log file using Wise Script
Use the Installation Log page to create an installation log and to specify its location and name. As an alternative, set the compiler variable _LOGFILE_PATH_ to the path of the log file.
The installation log is a text file that lists the events that occur while the installation runs. (Example: It contains the list of files that are replaced.) Entries are also added to the log when files are deleted or backed up, but the uninstaller does not take suchentries into account during rollbacks.
Select Installation Expert > Installation Log page and complete the page:
Do not create installation log: Mark this to prevent an installation log from being created. If you do this, the end user will get an error upon attempting to uninstall.
Create installation log in same directory as first installed file: This saves the installation log in the root, because the first Install File action is in the
uninstal.wse include script, which appears before any of your Install File lines. This option is included for backwards compatibility.
Create installation log in custom directory: Mark this to save the installation log in a directory you specify. This enables the options for selecting the directory. Select a directory and enter a name for the installation log in Install Log File Name. (Example: Install.log.) To create a new directory for the log within the Application or Windows directory, click New Folder.
Sunday, 5 August 2012
INSTALLDIR vs. TARGETDIR
INSTALLDIR represents the main product installation directory
TARGETDIR represents the installation directory for an administrative Windows Installer–based installation (when the user runs MsiExec.exe with
the /a command-line switch).
Subscribe to:
Posts (Atom)