I have a bespoke application which has no installer of it's own and the vendor suggests manual copy and configuration. This doesn't fit with the environment and delivery of existing applications, an MSI is our recommended approach.

The only issue is that there is a vendor initiated update process initiated by a Unix server, to change the process into a proper patch/upgrade isn't practical due to politics rather than technicalities. Part of the application, one key executable and 2 or 3 supporting files, are updated reasonably often by the UNIX server. Therefore I'd like to exclude that feature or the relevant components from Windows Installer self repair.

I've seen this question discussed before and there was mention of removing the component IDs for the respective EXE and DLLs. Are there any other options available? I'd like to be able support a complete uninstall and I'm not sure if that would be affected by some solutions.

A bit of background on why I do need some elements of self repair which if necessary could be moved to ActiveSetup if there was no alternative method.

Parent Feature - CurrentUser - HKCU application configuration - needs to be repaired as new users logon

[Sub Feature - CoreApp - Contains the ever changing application EXE and a couple of supporting files - linked to the Advertised Shortcuts

[Sub Feature - ODBC - ODBC configuration, ideally needs to support self-repair although isn't per user so will already be present as each new user logs on

Any advice on how best to approach this would be much appreciated.

Many thanks.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


To disable repair, remove the component's key path status.
Answered 03/31/2011 by: VBScab
Red Belt

Please log in to comment
Another solution:
1) Set condition to comonent: (NOT Installed) AND (NOT REINSTALL) (please check me)
2) Set "revaluate condition" option (flag) for component
Answered 03/31/2011 by: itolutions
Orange Senior Belt

Please log in to comment

Thanks for both the suggestions, I will try experimenting with both.

I had actually removed the component's key path for the application EXE (i.e. set it to none) and then found the advertised shortcuts that were linked to the EXE no longer deployed. What I'll do is try 'non-advertised' shortcuts instead.

The other solution I've not seen before but will be an interesting to try.

Thanks again.
Answered 03/31/2011 by: iainjo
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity