Some Needed Features

[moonshark413]

1 - Dialog settings do not include a Splash - we really need this one as found in the VS .NET 2003 Installer or InstallerVISE, just a dialog to show a JPG and "brand" our install up front.

2 - Billboards on the progress bar, InstallerVISE does a nice job of this but I dont know how to do it now that we are trying to standardize on MSI-based installations.

3 - Ability to set the Programs Menu name independent of the product name. We want our Company name in the Programs menu and the products installed beneath it. We have a historical location in program files that means we cannot use the manufacturer name in the install location (if the two are automatically related. This may be about automatic defaults, which are great for ease of use but please allow editing as well

4 - MSI and/or CAB names should be able to be indepent of the executable. We like to name our executables "Setup.exe" and the MSI a name based on the date and content (IE "1004_Legal" or "0930_Speeches") since we are installing various content for our reader application, and it provides a easy check for the support team that someone has the right CD. Packaging also gets to print more documentation that always says "Run Setup.exe" The VS2003 setup projects rely on a ini file to point the setup.exe to it's MSI files, that would be a good tactic for this option in your installer as well

5 - drag and drop support for adding files to folders.

6 - Why is the add folder dialog such an odd thing? Use the same dialog as for adding files...

7 - I'd like to have an installer finish and require the user to put in a second CD so the content there can be installed. Is this possible with AdvInst? I don't know how to do this in any package yet. It's related to a separate problem we have, that of installing our reader, then the content. Ideally, I'd like to do this so that uninstalling the app uninstalls the content (in a subfolder) as well, but modularly so that I can change the (VAST AMOUNTS) of content without mucking about with installer setup. Some sort of dynamic recognition of content sub-installers adjacent to the app installer

moonshark413@yahoo.com

[Cata]

Hi and thanks four your suggestions!

1) Nice idea -> to the list.
2) Same.

3) Done already. Edit the the Application Shortcut Folder in the Install Parameters page as you like. Select from the drop-down for some suggestions.

5) Already on the list.

4, 6, 7) Hmm, we'll think about them.

Cata

[Traction]

Hi, I would like to be able to import already compiled MSI Packages for editing. In my current situation we are using WinstallLE to repackage appications for distrubution but thus program has very limited functionality when it comes to applying file and folder permitions which the full version has aswell. For instance you must apply permitions to each individual file.

1) MSI File import

2) Hirachical assignment of permitions if this is not already supported.

Thanks.
Jeffrey

[Cata]

Thanks for your suggestions Jeffrey,

2) is on the todo list

I am afraid 1) is not very realistical, as importing an already created MSI into a AIP project is akin to decompiling a .exe back to the C++ code...

But we'll give it a try.

Cata