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
- :
- Re: Old filegroups in InstallShield pro 7.0
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
‎Jul 01, 2009
08:08 AM
Old filegroups in InstallShield pro 7.0
Hi, am upgrading from the old IS pro 7.0 to InstallShield express 2010.
A feature I can't seem to find is the ability for assigning certain attributes to filegroups with respect to upgrades. I had some file groups that were never to be overwritten on an upgrade, some if a newer version, if it was to be removed when uninstalling etc.
Where can I apply this in the 2010 version?
Cheers
Jim
A feature I can't seem to find is the ability for assigning certain attributes to filegroups with respect to upgrades. I had some file groups that were never to be overwritten on an upgrade, some if a newer version, if it was to be removed when uninstalling etc.
Where can I apply this in the 2010 version?
Cheers
Jim
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 01, 2009
04:17 PM
Filegroups were a concept specific to InstallShield Professional projects (now referred to as InstallScript projects in the Professional and Premier editions of Installshield). The Express edition does not support InstallScript projects, and therefore there is no equivalent option to filegroups available. Express builds MSI packages that install with the Windows Installer service. Windows Installer uses features and components to group the parts of an installation (note that Express only exposes feature level information, not components). During upgrades, Windows Installer makes the determination of whether to upgrade components or not (based on Windows Installer file versioning rules: http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 03, 2009
06:33 AM
Thanks Josh, I discovered the "installaiton/uninstallation" properties and "overwrite" properties can be set on a file by file basis.
I assume this determines Window installers decision whether to overwrite certain files during an upgrade or not?
I assume this determines Window installers decision whether to overwrite certain files during an upgrade or not?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 06, 2009
10:59 AM
The file overwrite properties either allow for the following:
- Windows Installer Versioning Rules: let MSI determine when a file should be installed/updated
- Never overwrite: if the file already exists, tells MSI to not install the file
- Always overwrite: Tricks Windows Installer into thinking the file always needs to be installed
There is a catch to using the always overwrite option in that Windows Installer may prompt for the original source media (such as during a maintenance/repair operation) since it will always attempt to install the file.
In general, Windows Installer excercises much tighter control over the installation process than was allowed with InstallScript/Pro installations.
- Windows Installer Versioning Rules: let MSI determine when a file should be installed/updated
- Never overwrite: if the file already exists, tells MSI to not install the file
- Always overwrite: Tricks Windows Installer into thinking the file always needs to be installed
There is a catch to using the always overwrite option in that Windows Installer may prompt for the original source media (such as during a maintenance/repair operation) since it will always attempt to install the file.
In general, Windows Installer excercises much tighter control over the installation process than was allowed with InstallScript/Pro installations.