New component not deploying file under minor upgrade

[raj@123]

Hi,

We have our installer in field right now and we supplies minor upgrades time by time.
Now we got one requirement to deploy one file conditionally but at the same location where it was getting deployed previously. So, what we did is that
1. we just removed that file from a component let say Component A.
2. We added a new component B with one condition.
3. Add that new file statically with 'Always Overwrite' option in the B component.

Now when ever we run that upgrade, this file is not getting deployed.
Can anybody tell us why is it happening and what would be its solution?

[DebbieL]

This community forum is for InstallShield 2008 Express Edition. Are you using the Express edition? The Express edition doesn't have a Components view, but the Premier and Professional editions do. So, I'll assume that you're using Premier or Professional.

A minor upgrade cannot delete a component. (For more info, see Major Upgrade vs. Minor Upgrade vs. Small Update (http://helpnet.acresso.com/Robo/BIN/Robo.dll?tpc=/robo/projects/installshield14helplib/MajorMinorSmall.htm).) Only a major upgrade can delete a component.

The following InstallShield 2010 help topic provides background on how Windows Installer determines whether a component and its files are reinstalled.
Overwriting Files and Components on the Target System (http://helpnet.acresso.com/Robo/BIN/Robo.dll?tpc=/robo/projects/installshield16helplib/FAQFilesOverwrite.htm)

So, for a minor upgrade, you may be able to simply update the file in the current component (without having to delete the old one and add a new one). It depends on whether the file is the key file of the component, whether it is a versioned file, etc.

I hope that helps.