[wix-users] Controlling Updates of unversioned files

[Todd Hoatson]

Edwin, thanks for the quick reply...

> Alternatively, install BYZ.p8z in a component that uses a different
versioned file as the KeyPath.

This is an interesting idea.  After considering this, I can see 3 possible
strategies:

Basic:
     Create a small dummy file which is versioned (i.e. a mostly-empty
.exe/.dll?) with a name like ForceUpdate.exe
     Make this file the KeyPath for its component
     Whenever we need an unversioned file to be unconditionally copied,
          Create a new version of the ForceUpdate.exe file
          Move the File element for the unversioned file into the same
component
          Build the installer
     At some (unspecified) point in the future
          Move the File element for the unversioned file back to its own
component
Better:
     Group unversioned files into logical sets
     Create a small dummy file which is versioned (i.e. a mostly-empty
.exe/.dll?) for each set
     For each set, move the File elements for the unversioned files into
the same component as the associated dummy file
     Whenever we need an unversioned file to be unconditionally copied,
          Create a new version of the dummy file for that set
Best(?):
     (Somehow) redesign our app to never distribute unversioned files

The third strategy seems attractive, in an ideal world, as it does not rely
on a kluge, but it would be a lot of work at this point.

Any comments on these three strategies?  Would you recommend any others?
Do you feel I have adequately understood your suggestion?

thanks,
Todd Hoatson
Mobile: 763-291-3312
Email:   todd.hoatson at gmail.com
www.linkedin.com/in/toddhoatson