InstallAware

Hi,

My InstallAware project has a dependency with Microsoft Windows Installer 3.1 and Microsoft Visual C++ Runtime 10.0. It has as statement to to Set Persistent Variable...

On a Windows 7 64 bit, when I install the software it installs fine and works fine.

When I first tried to uninstall the software from control panel, I hit the cancel button after the first dialog with a Uninstall button came up. The next time I tried to uninstall, it prompts for the dependent package should be installed and when clicked next on the dependency package installation form, it prompts with a folder browse dialog, trying to locate the Setup Source folder. It does not find it and hence uninstall fails.

The only way to uninstall after this state is to use the installer exe file and trying to install it during which it is able to locate the setup source folders.

IMPORTANT: If I remove the one line "Set Persistent Variable..." in my MSI code, then I don't have this problem. It uninstalls even after cancelling the first uninstallation. What relation could this have on the above mentioned behavior.

I have attached the InstallAware project and some screenshots for the above behavior. Hope it helps. We are at a crucial stage of a software release. So kindly respond at the earliest.

-Alex

Dear Alex,

I have not verified your project yet, but seems that you have not choosed to cache your Setup Sources.

have you tried to set as checked the "Always Cache Setup Sources" control in "Build Settings"?

This three-state check-box lets you control setup source caching. When the box is filled, the default source caching option (as described above for each build type) is in effect. When cleared, setup sources are never cached. When checked, setup sources are always cached.

Let me know.

Regards

Hi Francesco,

Thanks for you response. i can work around the issue with the way you mentioned. But is there a reason why this happens only if I have the "Set Persistent Variable..." line in the msi install code block.

Alex

Hi Francesco,

This solution just works around the finding of setup sources. But why is it needed to re-install Microsoft Visual C++ Runtime 10.0 while uninstalling the application.

And why would it prompt only when uninstalling the second time after we have cancelled the uninstallation first time.

Alex

Dear Alex,

honestly, I'm not quite sure if I full understand what you reported.

This solution just works around the finding of setup sources. But why is it needed to re-install Microsoft Visual C++ Runtime 10.0 while uninstalling the application
And why would it prompt only when uninstalling the second time after we have cancelled the uninstallation first time.

If I haven't missed nothing and without having your code, seems that by an error your VC runtimes installation it is istalled always even in maintenance mode. That it is strange and should not occurs.

Are you able to send me a very simple project that reproduces your behaviour?

Regards

Hi Francesco,

The one that is attached can reproduce this behavior. Could you please follow the steps in my first mail and let me know if it did reproduce the issue.

Alex

Dear Alex,

I will test your project and I will be back as soon as possible.

Regards.