pedrito
8/21/2007 4:17:00 AM
"Phil Wilson" <phil.wilson@wonderware.something.com> wrote in message
news:ef5ApB24HHA.5724@TK2MSFTNGP05.phx.gbl...
> The supported mechanism for updating an MSI product is another MSI update
> mechanism, like a patch MSP file or an update like Visual Studio's
> RemovePreviousVersions.
>
> Repair is an integral part of Windows Installer. A design that requires
> that it will never happen is unsafe. You can add DISABLEADVTSHORTCUTS to
> your MSI file with Orca. That will prevent routine repair via shortcut
> use, but there are lots of other things that will do an automatic repair
> if Windows thinks your product isn't installed as it should be. Also, you
> can't stop somebody right-clicking the MSI file and choosing Repair, and
> what about Add/Remove Prrograms "Click Here for Support Information" and
> the Repair button?
>
> --
> Phil Wilson
> [MVP Windows Installer]
Okay, that makes sense I guess. The problem is, I have data files that I
want to pre-install, but the user may want to delete some of those files,
which is an option available in my app. In fact, for the app to do what the
user wants, they must be able to delete these files. But when those files
get deleted and you run the app again, the installer reinstalls them. This
is clearly not MY user's desired behavior.
Is there no way around this? Some way to mark the items as "don't repair"? I
would have assumed marking them "Vital = false" would take care of that, but
apparently not.
As for repairing the app, that's fine if it reinstalls them, they can go
back in and delete them if they want. But I certainly don't want them
reinstalled every time the app runs. I can understand it being a feature,
but it also seems logical that it should be a feature you should be able to
disable for certain files.