This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: How to NOT replace a missing file during a repair.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 01, 2012
11:56 AM
How to NOT replace a missing file during a repair.
I know this is a odd request, but I'm near the end of a Minor Update to our software, and it's too late to switch to a Major to do this.
I have a component that installs a PDF form on our server. Apparently, I have been requested to NOT replace that file during a repair if it has gone missing. Currently, since it is a a component that should exist, the repair option will notice its absence and place the file back where it belongs, and someone is complaining.
doing this Is easy in my new installs, as I can just use a Custom Action to copy the file to the location (therefore not having a component) if it doesn't already exist. We are ok leaving the file there during an uninstall as well.
Does anyone have any words of wisdom?
My first idea is to break some conventions:
My Minor Update is also used as a new install, so my idea is
1) I do the new install copy trick when installing the feature for the first time (&Feature=3 condition)
2) I DELETE the component.... I know this is a no-no when it comes to best practices, but in reality what are the consequences? I believe the file would be ignored once the product is updated to the version missing the component, and then subsequent repairs would ignore the file (because it doesn't exist as a component).. are there any caveats I have missed?
Thanks for any and all suggestions.
I have a component that installs a PDF form on our server. Apparently, I have been requested to NOT replace that file during a repair if it has gone missing. Currently, since it is a a component that should exist, the repair option will notice its absence and place the file back where it belongs, and someone is complaining.
doing this Is easy in my new installs, as I can just use a Custom Action to copy the file to the location (therefore not having a component) if it doesn't already exist. We are ok leaving the file there during an uninstall as well.
Does anyone have any words of wisdom?
My first idea is to break some conventions:
My Minor Update is also used as a new install, so my idea is
1) I do the new install copy trick when installing the feature for the first time (&Feature=3 condition)
2) I DELETE the component.... I know this is a no-no when it comes to best practices, but in reality what are the consequences? I believe the file would be ignored once the product is updated to the version missing the component, and then subsequent repairs would ignore the file (because it doesn't exist as a component).. are there any caveats I have missed?
Thanks for any and all suggestions.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 01, 2012
09:15 PM
Sorry, you opened yourself up when you asked for "words of wisdom". I have many.
First, the requirement is bunk. I can pretty much read between the lines because I've had developers want the same thing. What's worst is they are asking for it late in their design when you are already trapped in a corner.
Bad, bad developers.
Your custom action tricks are hacks and are not good form. However, if you truely are fine with leaving a file behind on uninstall and not ever repairing it, the easiest thing to do I believe is to give the component a null guid.
First, the requirement is bunk. I can pretty much read between the lines because I've had developers want the same thing. What's worst is they are asking for it late in their design when you are already trapped in a corner.
Bad, bad developers.
Your custom action tricks are hacks and are not good form. However, if you truely are fine with leaving a file behind on uninstall and not ever repairing it, the easiest thing to do I believe is to give the component a null guid.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 08, 2012
03:31 PM
fair enough! I fought and lost the battle to get them to change their minds.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)