This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: how to custom action
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 28, 2009
10:56 PM
how to custom action
hello :
i am curious how many ways that define custom action ?
in InstallShield Professional 5.5 or earlier.define custom action between "program ","endprogram ".
in the install shield 12 or other new version .there is only way that event scripty to define custom action???
i am curious how many ways that define custom action ?
in InstallShield Professional 5.5 or earlier.define custom action between "program ","endprogram ".
in the install shield 12 or other new version .there is only way that event scripty to define custom action???
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2009
05:24 AM
it depends which type of project you use.
Basic msi is actually the best way to go. Here you can define different kinds of custom actions: installscript, vbscript, dll,....
Installscript project you need to use the event-driven approach...
I don't recommand the Installscript msi project type... 😉
Basic msi is actually the best way to go. Here you can define different kinds of custom actions: installscript, vbscript, dll,....
Installscript project you need to use the event-driven approach...
I don't recommand the Installscript msi project type... 😉
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2009
07:41 PM
hello:
thanks you answer!
i use IS12 and my project type is InstallInscrip.so there only event-driven to custom action?
thanks you answer!
i use IS12 and my project type is InstallInscrip.so there only event-driven to custom action?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 30, 2009
02:00 AM
Yes...
From the help of installshield:
Note
InstallScript installations are generally less desirable to systems administrators because they require the use of Setup.exe, rather than being self-contained in an .msi file, and may not be fully customizable prior to deployment. If your software will be customized by corporate systems administrators prior to deployment, Macrovision recommends that you create a Basic MSI installation project.
The InstallScript Engine
With InstallScript projects, the run-time user interface is rendered and its flow controlled by InstallScript, and the changes that are made to the target operating system are done through InstallShield’s trusted InstallScript engine, with no reliance on Windows Installer.
Using InstallScript as the installation driver has many benefits. The first is that InstallScript’s event model enables you to create a script-driven installation without writing a single line of code. If you want to add custom functionality, you need to implement only the events whose functionality you want to change.
The user interface abilities for Basic MSI projects are somewhat limited with regard to the types of controls you can use or the kind of control you have over dialog events. InstallScript projects have no such limitation—offering a wide range of standard controls along with the ability to add custom dialog controls. Dialog messaging in the script enables you to have complete control over how your end-user dialogs behave.
From the help of installshield:
Note
InstallScript installations are generally less desirable to systems administrators because they require the use of Setup.exe, rather than being self-contained in an .msi file, and may not be fully customizable prior to deployment. If your software will be customized by corporate systems administrators prior to deployment, Macrovision recommends that you create a Basic MSI installation project.
The InstallScript Engine
With InstallScript projects, the run-time user interface is rendered and its flow controlled by InstallScript, and the changes that are made to the target operating system are done through InstallShield’s trusted InstallScript engine, with no reliance on Windows Installer.
Using InstallScript as the installation driver has many benefits. The first is that InstallScript’s event model enables you to create a script-driven installation without writing a single line of code. If you want to add custom functionality, you need to implement only the events whose functionality you want to change.
The user interface abilities for Basic MSI projects are somewhat limited with regard to the types of controls you can use or the kind of control you have over dialog events. InstallScript projects have no such limitation—offering a wide range of standard controls along with the ability to add custom dialog controls. Dialog messaging in the script enables you to have complete control over how your end-user dialogs behave.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 30, 2009
07:31 PM
thank you very much .i get it.
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)