Update not installing root APPDIR files

[jfuhr]

When I run my installer as a fresh install, it works perfectly. However, if a previous version is installed, the new installer installs all files *except* for the root files in APPDIR.

I have checked Organization and the the root files are in MainFeature.

The only change I recently made was to use the Persistent User Data wizard for one file.

What else should I check? I've attached the .aip in question.

Thanks

[mihai.petcu]

Hello,

This could happen if you somehow modified the GUID of the files' components. For example by enabling and disabling Synchronized folder option after changing versions.
If you used the Persistent User Data wizard, the "Install new version first and then uninstall old version" was enabled by default and if the components don't have the same GUID they will be deleted.

You can try to assure the components from the MainFeature have the same GUIDs between versions and see if the behavior persists.

All the best,
Mihai

[jfuhr]

Thanks for the response.

I checked the GUID for the Component and it was different. I changed the GUID to match the previous version, but it is still deleting the component files.

Also, the "Do not register this component with Windows Installer" is not checked.

Is there anything else I can check or do I have to do something to make the new GUID take effect?

[mihai.petcu]

Hello,

This should work unless there is something else causing this. You could try to recreate the upgraded version using the correct approach:
- backup the previous version
- change the version( select Yes when prompted to change the Product Code )
- upgrade the resources of the synchronized folder on the hard drive
- refresh folder
- use Persistent User Data

If this is not an option for you, can you please send us the .AIPs( previous and upgraded version ) and a verbose log of the upgrade installation to support at advancedinstaller dot com so we can investigate them?

All the best,
Mihai

[jfuhr]

I thought I would post Cosmin's resolution in case somebody else runs into this issue.

To summarize, when I used the Persist User Data feature, it moved the target file into it's own component and designated another file to be the key member of the original group. This was because the file that was moved was also the key member. Dragging the file back to the original component and making it the key member resolved the issue.

I think this was a fluke incident because the user persisted file also happened to be the key member of the previous version's component.

Cosmin's response:

Windows Installer evaluates components based on their key members (the
one with a key icon overlay in Organization page).

I noticed that "Default.aspx_3" component used "CustomerSettings.config"
as keypath in your old version and uses "CustomerSearch.aspx" in your
new version. Also, "CustomerSettings.config" is now in a separate
component.

Please try this:
- go to Organization page
- drag "CustomerSettings.config" resource from "CustomerSettings.config"
component to "Default.aspx_3" component
- right-click "CustomerSettings.config" resource
- select "Make Key Member" context menu item
- save and build your project

The persistent user data feature is very sensitive when it comes to
components:
http://www.advancedinstaller.com/user-g ... rades.html

So you need to make sure that your new package maintains the original
component layout.

Regards,
Cosmin