I have a clean InstallScript project that turns out to be problematic due to this problem . This was temporarily resolved by adding some InstallScript that wipes the specific directory before new files are installed, which is not ideal. However, this series of forum posts indicates that the InstallScript MSI project or the main MSI project will greatly simplify the removal of dynamically linked files during the upgrade.
Searching the Flexara forums, I find many posts related to the InstallScript MSI project type, so I look at Basic MSI. Flexara seems to have a product called Repackager that can convert InstallScript projects to Basic MSI . However, it only comes with IS Premier or an admin studio, which means we have to spend some money. Before going down this road, I need to point out that this might work.
- Can I lose any functionality when converting from InstallScript to Basic MSI using the Repackager tool? We have a bit of logic in our scripts, including things like this , which convey information at several stages of the installation. We also use several ServiceShield NT objects, obsolete objects, which, it seems to me, had to be installed separately from IS2010. Are there any aspects of InstallScript projects that are not known to use Repackager?
- If Repackager is not going to magically convert the project, is there a guide somewhere that I can follow to do the conversion manually? I found the documentation and InstallShield forums are pretty tough not enough.
- Is there any way to get the basic MSI installation package for installing updates on systems where the old (clean version of InstallScript) is installed? It really will be a bonus. At this point, I expect that we will simply be forced to completely remove / reinstall.
source
share