Migrate from Installanywhere

[Rawand]

Hi,
We are currently using installanywhere and trying to migrate to AdvancedInstaller , I wondered if we can upgrade the previous version that created with installanywhere? because it doesnt have .msi file. if its possible then please tell me how, otherwise any suggestions will be apreaciated.
Regards

[Cosmin]

Hi,

If the installation you want to remove is not MSI-based (they are not created by using the Windows Installer technology) then you can uninstall it only by using a custom action.
This custom action can call the Uninstaller of the old installation (if it has one), or it can search an remove all the resources of the installation (I'm not sure how exactly this custom action would look like, but I'm sure it can be done).

Regards,
Cosmin

[Rawand]

its interesting, but one issue is remaining, how to call the Uninstaller of the old installation(which is an .exe file) ?

Regards

[Cosmin]

Hi,

The Uninstaller of the old installation can be launched by using a "Launch file or open URL" custom action. This custom action can be scheduled under the "RemoveExistingProducts" standard action and it can use the condition NOT Installed.

Regards,
Cosmin

[Rawand]

Thanks, can i give the Uninstaller file a dynamic path tobe getted from some property? and when its launched it give a errer message 'Installanywhere properties file is missing' but when i test the Uninstaller amnually it was ok, any idea why?

[Cosmin]

Hi,

Most likely the uninstaller needs another file next to it. In order to launch it successfully you can follow these steps:
- go to the Install Parameters page and create the UNINSTALLER_FOLDER property (the value doesn't matter)
- go to the Files and Folders page and create a property-based folder using UNINSTALLER_FOLDER
- go to the Search page and create a search for the Uninstaller
- name the search UNINSTALLER
- go to the "Custom Actions" page and under "InstallExecuteSequence" -> "AppSearch" create a custom action which gets the parent folder of the file
- this custom action can use the "Session.Property" method to set the UNINSTALLER_FOLDER property to the path of the folder which contains the uninstaller; for example:

Code: Select all

Session.Property("UNINSTALLER_FOLDER")=fso.GetParentFolderName(Session.Property("UNINSTALLER"))

- under the "RemoveExistingProducts" standard action create an "EXE with working Dir" custom action which is configured like this:

• Working Dir: UNINSTALLER_FOLDER
• Full Path: UNINSTALLER
• Execution Properties: Synchronous execution, check return code
• Execution Options: Immediate execution
• Scheduling Options: Always execute
• Expression: NOT Installed

Let me know if the problem persists when using this approach.

Regards,
Cosmin

[Rawand]

one more question, Working Dir: must be set to only a specific folder on destination computer and its not editable , still not working

[Cosmin]

Hi,

The working directory of the EXE must be a folder in the package.

In my previous post I made a mistake (it's corrected now): in the "Files and Folders" page you create a property-based folder by using the UNINSTALLER_FOLDER property, not the UNINSTALLER property. This way you will be able to set UNINSTALLER_FOLDER as the working directory.

Note that in order to do this you must specify the UNISTALLER_FOLDER property in the Install Parameters page (the value doesn't matter because it will be set by the custom action).

Regards,
Cosmin