InstallShield 2012 wishlist

[Server]

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...

[Roman1]

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

[#3]

9. Bootstrapper support 32bit/64bit installation at one package.

[svengalamr]

9. Please take care of IIS related issues. We are facing few issues with IS 2011, Windows user passwor dis getting corrupted in IS2011

[eseilram]

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..

[sriprathikka]

11.) Installscript project type unable to overwrite the application exe version in Setup.exe file properties.

[LanceRas]

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.

[tw0001]

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.

[Server]

13) Comment and/or answer from Flexera Software regarding future development plans for InstallShield product. Communication with developers and participation in this thread. :mad:

[jwallenstein]

19. Build to ISScipt setups the same prerequisities workaround as in MSI-Setups

Thanks
Jan

[jwallenstein]

20. The logic of text editor such colours, tabs, bookmarks should be similar to MS-Visual Studio

[Server]

21. .NET custom actions editor integrated and WIX DTF integration possibility (at least it is only usable .NET custom actions solution).

[jwallenstein]

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

[jwallenstein]

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.

[jwallenstein]

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.

[jwallenstein]

25. Let us use also in the future InstallScript Objects.
Do not discard this feature!

[jwallenstein]

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.

[jarcinfo]

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

[jwallenstein]

29. Simplify developing and creating dialog sequences in UI.

[jwallenstein]

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.

[bbrriijj]

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.