Atlas
Posts: 30
Joined: Sun Mar 16, 2008 11:08 am

Love the product! Have a few questions...

For a number of years I've been an InstallShield customer, doing my best to ignore unfixed bugs and unresponsive customer support. Finally I decided to download the demo of Advanced Installer, and have been pleased to find a product of higher quality, lower price, and better support. 8) But I do have a few questions that have come up during my evaluation:

1. I want to create a subfolder in Common Application Data that frees up the rights so that my app can play around in it without admin privileges. In InstallShield I could set the same user-friendly rights that Windows presents to the user in Windows Explorer (Full control, Modify, Read & execute, List folder contents, Read, Write, and Special permissions). In Advanced Installer I'm presented with a much more comprehensive and cryptic list of permissions that I'm having difficulty understanding. What is the best set of rights to select to allow my app to create/delete/read/modify/list files and folders? Googling has so far provided 4 alternatives:

- Generic Read, Generic Write, Delete
- Generic All, Generic Read, Generic Write, Generic Execute
- Generic All, Generic Read, Generic Write, Generic Execute, Standard Rights All
- Read Control, Delete, Write DAC, Write Owner, Specific Rights All, Generic Execute, Generic Write, Generic All

(As a feature request I'd ask for a combobox that would let me select from a few professionally-created set of rights for common scenarios, or the same user-friendly options that Windows Explorer uses. An explanation of what these rights mean in the help would be cool too.)

2. It appears that Advanced Installer has two ways of adding a EULA...in the Prerequisites page and in the Dialogs page. Do the two techniques have advantages over each other?

(As a feature request, I'd ask that the help for each of the two methods of adding a EULA would mention that there's also another way to add a EULA, and how they are different.)

3. Advanced Installer doesn't provide default download links for the .NET redistributables, reportedly because Microsoft changes the URLs. Where is the recommended place to link these files? Should I link to Microsoft's copies? Should I host my own copies?

Thank you very much for any help!
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
What is the best set of rights to select to allow my app to create/delete/read/modify/list files and folders?
Currently the permission options are the ones used directly by Windows Installer. However, we have on our TODO list an improvement which will allow you to choose between more clearer options.

Also, please note that by default a normal user has write and read access in the "Common Application Data" folder.

If you decide to use the Permissions feature, you can configure it like this:

If you want to specify the standard *Read* permission, check the following:

Code: Select all

READ_CONTROL
FILE_READ_DATA
FILE_READ_ATTRIBUTES
FILE_READ_EA
If you want to specify the standard *Read & Execute* permission, check the following:

Code: Select all

READ_CONTROL
FILE_READ_DATA
FILE_READ_ATTRIBUTES
FILE_READ_EA
FILE_EXECUTE 
GENERIC_EXECUTE
If you want to specify the standard *Write* permission, check the following:

Code: Select all

READ_CONTROL
FILE_WRITE_DATA
FILE_APPEND_DATA
FILE_WRITE_ATTRIBUTES
FILE_WRITE_EA
GENERIC_WRITE
If you want to specify the standard *Modify* permission, check the following:

Code: Select all

READ_CONTROL
DELETE
FILE_READ_DATA
FILE_READ_ATTRIBUTES
FILE_READ_EA
FILE_EXECUTE
FILE_WRITE_DATA
FILE_APPEND_DATA
FILE_WRITE_ATTRIBUTES
FILE_WRITE_EA
GENERIC_EXECUTE
GENERIC_WRITE
If you want to specify the standard *Full Control* permission, check the following:

Code: Select all

READ_CONTROL
DELETE
WRITE_DAC
WRITE_OWNER
SPECIFIC_RIGHTS_ALL
GENERIC_EXECUTE
GENERIC_WRITE
GENERIC_ALL 
2. It appears that Advanced Installer has two ways of adding a EULA...in the Prerequisites page and in the Dialogs page. Do the two techniques have advantages over each other?
We implemented this feature in both parts of the installation package (the bootstrapper and the actual MSI) in order to allow our users to present an EULA in the early stages of the installation.

For example:
1) The user creates only a MSI package (without a bootstrapper). In this case he will use the "LicenseAgreementDlg" dialog in the "Dialogs" page.

2) The user creates a MSI package with some third party prerequisites. In this case he can use "LicenseAgreementDlg" dialog because the third party prerequisites have their own EULAs.

3) The user creates a MSI package with some prerequisites created by him or his company. In this case he can display the EULA in the early stages of the installation instead of showing it in the main installation.

Note that this feature has been added in order to allow you to have more control over the installation package. Also, only you can determine which option is best suited for your installation package.
As a feature request, I'd ask that the help for each of the two methods of adding a EULA would mention that there's also another way to add a EULA, and how they are different.
We will consider improving the help files in the future. Thank you for your suggestion.
3. Advanced Installer doesn't provide default download links for the .NET redistributables, reportedly because Microsoft changes the URLs. Where is the recommended place to link these files? Should I link to Microsoft's copies? Should I host my own copies?
Since the Microsoft download links change from time to time, then the answer to your questions is this:
1) If you plan on distributing the same installation package for a long period of time then it is recommended that you host the installation file on your server. In this case the prerequisite will always point to the file on your server.

2) If you plan on distributing different installation packages for short periods of time (for example, you release full upgrade packages very often), then you can use the Microsoft links. In this case, if a link changes at Microsoft you will also change it in your package.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Atlas
Posts: 30
Joined: Sun Mar 16, 2008 11:08 am

Cosmin, thank you very much for posting how the Windows Installer permissions correspond to the user-friendly Windows permissions. That's exactly the type of information I needed but was unable to find!

Return to “Common Problems”