(Un)Install MSI Setup

[wxperson99]

Hi,

Will the (Un)InstallMSI command uninstall previous installations created with the NATIVE_ENGINE = TRUE ?

THanks,

George

[FrancescoT]

Dear George,

No at all!

The (Un)InstallMSI command can be only used to install/uninstall a setup package based on Windows installer Engine.

With a Native Engine based installer use the Run Command and then to uninstall the package, execute the setup.exe as below;

<setup.exe> /s MODIFY=FALSE REMOVE=TRUE (/S = silent mode).

Hope this helps you.

Regards

[wxperson99]

OK... thanks for the reply.

If I can clarify for my own benefit.

I have install A called aaa.exe and an install B called bbb.exe

I install A in January and then in June I want to install B but first uninstall A.

I would use the run command near the start of install B to execute the following command.

Run Program aaa.exe /s MODIFY=FALSE REMOVE=TRUE

If this is correct then I will need to make sure the installation file aaa.exe file remains on the PC after the install A is done... correct?

Thanks,

George

[FrancescoT]

Dear George,

just a question; are you uninstalling a different version of a same product?

Eg; A= MyProduct 1.0 and B= MyProduct 2.0 ?

If true, it's not necessary do write any extra code. The installation of MyProduct 1.0 or MyProduct 2.0, will replace automatically any different version of the same product (...ìf any installed and supposing that both installer share the same identical; PRODUCTCODE and UPGRADECODE, but a different REVISIONCODE).

Of course if for some reasons you need to forcibly remove an existing installation, you may run that command before to proceed with the effective installation of the other package.

It's not necessary to leave the setup.exe on the target machine. Once installed, a copy of it is Always cached on the target machine. To keep track of it, store somewhere the value of the UNINSTALLLINK pre-defined variable. Then read the stored value from the other installer. The value points to the exact location of the cached setup.exe on the target machine.

For more details, have a look at the InstallAware documentation.

Hope this helps you.

Regards

[wxperson99]

OK.. I think I understand.

I suppose I could put the UNINSTALLLINK into the registry somewhere.

Another question.

How does the uninstall MSI command work when you have a hybrid install. i.e. Native_engine = false (MSI) with a few areas where you use the native_engine (true)?

Thanks,

George

[FrancescoT]

Dear George,

in this case, the installer is a standard MSI installer based on Windows Installer Engine. So the uninstall MSI command will work.

Supposing, you used NATIVE_ENGINE = TRUE with a few areas and that "Apply Install" gets called when NATIVE_ENDIGINE is not active (FALSE).

Regards

[mehran]

Hi there.

We use Native Engine and I know that we should use Run Command to uninstall a product instead of using (Un)InstallMSI command in Native Engine.

The problem we have is when we use (Un)InstallMSI command it displays details of uninstalling the product in the progress dialog, but when we use Run Command, there is no interaction between installer and the product that being uninstalled, and we cannot display details in the installer's progress dialog.

This makes the user think that the installer is stuck and is not doing anything.

Is there a way I can capture details of an installer in this situation and display it to the user?

Thanks