Product code different in project than msi

[ccamp31]

Hello,

I have an IA project where it lists a product code in the 'Project Properties' section. When I generate an .msi using the Group Policy Wizard, the .msi has a completely different product code.

The issue is, when I install the .msi, it creates an uninstall key for both product codes (the one associated with the project, and the one for the .msi).

So my question is:

a) Is this a bug in InstallAware?
b) If not, how can I prevent my .msi from installing both product codes into the uninstall key in the registry?

Cheers,

Chris

[giaviv]

Hi Chris,

This is actually not a bug - your product code does exist in the inner MSI, which is wrapped by an EXE, which is wrapped by the group policy MSI.
Where is this uninstall key being created?

[ccamp31]

Both uninstall keys were installed to the registry at (Windows 7 target machine):

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

I was able to get the installer to only install one key, when I inserted the following statement in my MSI code:

Set Variable NATIVE_ENGINE to TRUE

Now I only see one uninstall key in the registry - are there any downsides to activating the native engine?

Cheers,

C.

[giaviv]

Not at all, to the contrary - the Native Engine is much more powerful than the Windows Installer one.

[ccamp31]

Not at all, to the contrary - the Native Engine is much more powerful than the Windows Installer one.

I just noticed a problem with my installer once I turned the Native Engine on - it no longer installs my Windows Install Service. If I don't set the Native Engine to TRUE, the service installs without issue.

Do you know why this is happening?

Cheers,

Chris

[giaviv]

Chris,

This should be happening - are you able to check if turning the native engine off right before installing the service, and turning it back on after solves the issue?

[giaviv]

Chris,

This should be happening - are you able to check if turning the native engine off right before installing the service, and turning it back on after solves the issue?

[ccamp31]

Turning it off only works if I don't turn it back on before the last step (Apply Install). However, by leaving it off when it reaches 'Apply Install', I have other issues (for example, it installs 2 product codes in the uninstall key in the registry - one for the inner msi, and one for the outer).

Why would having the Native Engine turned on disable the ability to install a service? Wouldn't that be considered something fairly standard?

Chris

[giaviv]

Chris,

It should work with the native engine too, but I am trying to see if the native engine is the issue or not.
You can try calling apply install more than once - are you able to narrow the problem down to the native engine?