Advanced Installer Community

BPeters

I created an msi for my application. When I ran the installation there was some error that caused the installation to stop unexpectedly (error was my fault). Add/Remove Programs would not allow me to uninstall so I used msizap to clear my machine so I could reinstall. All now works fine except any ...

BPeters

Ahh. I thought the patch was patching the already installed application not the cached msi file. This makes sense now.

Thanks,
Brad

BPeters

I created a 2 test installs that simply install a txt file then the newer version has different text. When I run the patch on these 2 it works find with a simple repair. When I click modify the Main Feature is set to install locally. However on the installs where I get the patch failure the Main ...

BPeters

I have created and Install with product version 1.0.0 and then a second install with product version 1.0.1 this is a minor change (fixed bug in exe) so I did not change the Product ID when creating the new Install. To create the install for the new version I copied the aip file and all my source ...

BPeters

Now that I have posted I managed to find the solution myself.

You can condition custom actions that are sequenced after InstallValidate to handle major upgrades by using the UPGRADINGPRODUCTCODE property:

If you want a custom action to run during an uninstallation of the product, but not during ...

BPeters

Is there any way I can have a Custom Action run only on an Uninstall not on and Upgrade. This custom action cleans up a database and if upgrading application I don't want to perform this action but if uninstalling I do. Is there some conditions I can set to accomplish this.

Thanks,
Brad

BPeters

Well I found a solution and thought I would post incase someone else had the same problem. All I had to do is when I set the custom action I want to occur after the Registry Keys are removed to be under Uninstall and execute on Commit set the Executions Properties to be Synchronous execution, ignore ...

BPeters

After working on this problem for some time I have found that the search is preformed only on Install so that won't work. So I searched the help and found a post that suggests using MsiGetProperty to obtain property information from a DLL. I got that to work but am now trying to use MsiSetProperty ...

BPeters

When I set the custom action under Uninstall I have to set it to execute on commit. Before commit the registry values are still there. The problem now is that when I execute on commit the DLL containing the custom action is removed. This DLL is reference counted and used by other installs so this ...

BPeters

Where do I add my custom action so it will run on an uninstall after the registry keys for that install have been removed.

Thanks
Brad

BPeters

I have 2 different installs for the same application one for each language. When the second one installs I would like not display the folder dialog so it will install the additional language files into the same dir as the original install. I would like for the applications to be installed in either ...

BPeters

I have created a test install to try and figure out the component conditions. My installation has 4 files divided into 2 components.

Component 1 is "Sunset.jpg" with Sunset.jpg and Blue hills.jpg
Component 2 is "Water_lilies.jpg" with Water lillies.jpg and Winter.jpg

Component 1 sets the files ...

BPeters

I am also curious how you would go about disableing the Modify option when an msi file is run after it is installed. Ideally I would like to stop the user from repairing or modifying once installed successfully.

Thanks
-Brad

BPeters

My installation contains 3 files that are needed only for installation. They are accessed from a custom DLL and then deleted by the DLL. However when the application is repaired the 3 files are restored.

1. Is there a way that I can set the component properties under organization so that the files ...

BPeters

With a little more testing I found that when I created by second install file I simply copied the first. This left the GUID the same for the exe in both installs. By creating a new project from scratch this shortcut being left behind is solved.

Suggested Articles

User Guide

Videos

Refer & Save Up to 30% On Your Renewal

Search found 17 matches

Uninstall leaves behind reference counted files

Problem with Patches

Custom Action on Uninstall not on Upgrade

Custom Action after Registry remove

Dynamically Show/Hide Dialogs

Repairing and Feature Conditions

Caphyon Products

Company

Product

Resources

Free Tools

Connect

Community