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
- :
- InstallShield 2012 wishlist
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
‎Mar 31, 2011
07:50 AM
InstallShield 2012 wishlist
Hello,
I would like to start to collect user requirements related to InstallShield 2012 in this thread. Please post your suggestions and proposals.
And when it comes to us:
1. Setup.exe supporting multiple product installation (customization of the products to be installed and etc.);
2. Make parts of the InstallShield functionality re-usable and re-distributable from WIX DTF custom actions as .NET libraries;
3. InstallShield Automation interface - provide simple example code in the documentation, how to add components to the InstallShield project and so on.
3. TFS integration should be improved - ready to use TeamBuild automation template(targets?) and examples of the implementation;
4. VisualStudio UI should be faster;
5. Solve licensing headaches with Standalone Build;
6. Lower price ~20% - realistic, but in fact 30-40 needed to follow the market. Maybe step by step.
That is what we initially need...
I would like to start to collect user requirements related to InstallShield 2012 in this thread. Please post your suggestions and proposals.
And when it comes to us:
1. Setup.exe supporting multiple product installation (customization of the products to be installed and etc.);
2. Make parts of the InstallShield functionality re-usable and re-distributable from WIX DTF custom actions as .NET libraries;
3. InstallShield Automation interface - provide simple example code in the documentation, how to add components to the InstallShield project and so on.
3. TFS integration should be improved - ready to use TeamBuild automation template(targets?) and examples of the implementation;
4. VisualStudio UI should be faster;
5. Solve licensing headaches with Standalone Build;
6. Lower price ~20% - realistic, but in fact 30-40 needed to follow the market. Maybe step by step.
That is what we initially need...
(58) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2011
09:16 AM
7.
Please make the posibility to set file flag
"always overwrite"
for files dynam. linked.
It is possible to patch a build msi.
We set file version to 65353.0.0.0 , even for dynamic linked files.
8.
Let us use TFS Source Control within ISdev. Not only from MS-Visual Studio.
Make configurable the menue Project/Source Control
Please make the posibility to set file flag
"always overwrite"
for files dynam. linked.
It is possible to patch a build msi.
We set file version to 65353.0.0.0 , even for dynamic linked files.
8.
Let us use TFS Source Control within ISdev. Not only from MS-Visual Studio.
Make configurable the menue Project/Source Control
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2011
01:00 AM
9. Bootstrapper support 32bit/64bit installation at one package.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2011
04:24 AM
9. Please take care of IIS related issues. We are facing few issues with IS 2011, Windows user passwor dis getting corrupted in IS2011
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 01, 2011
05:27 AM
Support
- ShortCut for each Instance
- INSTALLDIR for each Instance
in an easy way, perhaps as MultiInstance Property
I think that's something every installation needs..
- ShortCut for each Instance
- INSTALLDIR for each Instance
in an easy way, perhaps as MultiInstance Property
I think that's something every installation needs..
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 04, 2011
07:23 AM
11.) Installscript project type unable to overwrite the application exe version in Setup.exe file properties.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 05, 2011
05:59 PM
13. Predefined path to the ALL USERS > SHARED DOCUMENTS path. Currently the only way to use that path is to use Installscript to obtain the Windows API path and then set a property.
14. Pro version have ability for custom themes (or at minimum, the ability to have one predefined custom theme name/location to edit/use for builds).
15. Acrobat Reader X detection and prerequisite.
16. Internet Explorer 9 detection and prerequisite.
17. Project option to force all files added via the basic interface to be in stored seperate components as key files. (Understanding that with very large installs, this would not be optimum, but for smaller projects, it would be fine).
18. In the prebuild process, compress specified files using UPX. Similar functionality as in Builds options to codesign selected files/files of type, except to compress EXE's using UPX. This would need to be, obviously, executed in the build process before codesigning.
14. Pro version have ability for custom themes (or at minimum, the ability to have one predefined custom theme name/location to edit/use for builds).
15. Acrobat Reader X detection and prerequisite.
16. Internet Explorer 9 detection and prerequisite.
17. Project option to force all files added via the basic interface to be in stored seperate components as key files. (Understanding that with very large installs, this would not be optimum, but for smaller projects, it would be fine).
18. In the prebuild process, compress specified files using UPX. Similar functionality as in Builds options to codesign selected files/files of type, except to compress EXE's using UPX. This would need to be, obviously, executed in the build process before codesigning.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 06, 2011
01:59 PM
my request for Basic MSI projects:
possiblity of getting this directory structure in a release configuration:
1) setup.exe (includes setup.ini, prerequisites, all mst and language ini files but not the MSI file)
2) Program.msi (where program is your msi name)
currently you can get (1) setup.exe, loose mst files, loose ini files, msi, and cab files (I don't want the cab file), or (2) setup.exe on its own with the MSI and everything else embedded. I'd rather have the MSI separate from the setup.exe but have the setup.exe with everything else in it.
possiblity of getting this directory structure in a release configuration:
1) setup.exe (includes setup.ini, prerequisites, all mst and language ini files but not the MSI file)
2) Program.msi (where program is your msi name)
currently you can get (1) setup.exe, loose mst files, loose ini files, msi, and cab files (I don't want the cab file), or (2) setup.exe on its own with the MSI and everything else embedded. I'd rather have the MSI separate from the setup.exe but have the setup.exe with everything else in it.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2011
08:21 AM
13) Comment and/or answer from Flexera Software regarding future development plans for InstallShield product. Communication with developers and participation in this thread. :mad:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 11, 2011
07:00 AM
19. Build to ISScipt setups the same prerequisities workaround as in MSI-Setups
Thanks
Jan
Thanks
Jan
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 13, 2011
08:09 AM
20. The logic of text editor such colours, tabs, bookmarks should be similar to MS-Visual Studio
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 17, 2011
03:08 PM
21. .NET custom actions editor integrated and WIX DTF integration possibility (at least it is only usable .NET custom actions solution).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 19, 2011
02:32 AM
22. Please make the possibility to start extern application
just after MSI-Setup ends. It should be possible to trigger
this action not only from dialog "Setup Finish" but in silent (/q)
setup dialogless too.
Thanks
Jan
just after MSI-Setup ends. It should be possible to trigger
this action not only from dialog "Setup Finish" but in silent (/q)
setup dialogless too.
Thanks
Jan
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 20, 2011
06:50 AM
23. Please let us formatting Text Area Control in ISScript project
similar as in MSI-Project. Now, it is not possible to set text color and font.
similar as in MSI-Project. Now, it is not possible to set text color and font.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 26, 2011
06:42 AM
24. InstallScript - Setups:
Rewrite function nCmdValue = WaitOnDialog(szDialogName);
It should return all Windows messages not only WM_COMMAND.
Or write another function
WaitOnDialogEx(szDialogName, HWND, szMsg, wParam, lParam);
(HWND, szMsg, wParam, lParam - are return values)
which works similar to WaitOnDialog and does return all messages.
Rewrite function nCmdValue = WaitOnDialog(szDialogName);
It should return all Windows messages not only WM_COMMAND.
Or write another function
WaitOnDialogEx(szDialogName, HWND, szMsg, wParam, lParam);
(HWND, szMsg, wParam, lParam - are return values)
which works similar to WaitOnDialog and does return all messages.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 27, 2011
09:47 AM
25. Let us use also in the future InstallScript Objects.
Do not discard this feature!
Do not discard this feature!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 29, 2011
06:38 AM
26. Prerequisite Condition Builder
Let us build conditions connected with "or" not only "and" operator.
Use the same logic as condition builder in msi CA projects.
Let us build conditions connected with "or" not only "and" operator.
Use the same logic as condition builder in msi CA projects.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 02, 2011
09:46 AM
27 - Prerequisite editor:
a - New type of condition: external check, to allow the call to an external program and the use of its exit code for the condition test
b - More available properties to the setup launcher (today we dispose of SETUPEXEDIR, ISPREREQDIR, etc. ) : by sample, the user temporary folder would be very usefull to create a named log file ...
c - When prerequiste is "Copy from source media", allow to locate it at another path than "ISSetupPrerequisites"
28 - Windows Server 2008 R2 where remote Desktop Service is configured: allow the installation of chained msi MSI (without to have to write custom code to workaround or to modify the local group policies) - CF. issue IOA-000055518
a - New type of condition: external check, to allow the call to an external program and the use of its exit code for the condition test
b - More available properties to the setup launcher (today we dispose of SETUPEXEDIR, ISPREREQDIR, etc. ) : by sample, the user temporary folder would be very usefull to create a named log file ...
c - When prerequiste is "Copy from source media", allow to locate it at another path than "ISSetupPrerequisites"
28 - Windows Server 2008 R2 where remote Desktop Service is configured: allow the installation of chained msi MSI (without to have to write custom code to workaround or to modify the local group policies) - CF. issue IOA-000055518
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 05, 2011
01:40 AM
29. Simplify developing and creating dialog sequences in UI.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 09, 2011
02:50 AM
30. Predefine a Target Path to the "Program Files" on x64 OS, even when the main setup is created as x86 - MSI . Now, it is possible to do using CA.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 11, 2011
12:13 AM
26. Have the ability to create individual cab files for individual features. That will fecilitate users to download only required cab files rather than the entire install. It will be a great help for installs which are large in size.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)