(maybe a very-basic question)
I built an MSI setup using Visual Installer.
After having installed on the target PC, if I try to delete/rename one of the files included in the packet, the MSI starts and looks for restoring the missing file.
(for instance the final user may delete some of the sample files included in the package)

How can I mark some of the files as non-vital?
Is it possible using Visual installer?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I don't know how to use Visual Installer, but I can explain the sorts of things that you need to do to avoid this problem.

Firstly, if the files are not required by the main program, then move those components into a separate feature called "Samples" (does Visual Installer allow you create packages with multiple features?). When you run the main program, it will only check the components in the same (and parent) feature/s.

Another alternative (which you may use in conjunction) is to have the sample folder as the key for the component instead of the actual sample file. My first suggestion should make this unnecessary.
Answered 04/15/2004 by: mrtap
Senior Yellow Belt

Please log in to comment