pavel1.5524893713569453E12 asked a question.
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&37; - realistic, but in fact 30-40 needed to follow the market. Maybe step by step.
That is what we initially need...
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
- ShortCut for each Instance
- INSTALLDIR for each Instance
in an easy way, perhaps as MultiInstance Property
I think that's something every installation needs..
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.
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.
Thanks
Jan