I made a smart client application with automatic updates throught version
numbers. This application is installed using a .msi file generated with a
.net setup project in visual studio .net 2003.
When I change the version numbers three times, the first installation is
deleted, and the msi automatically reinstall it, then corrupting the
configuration files and also the application.
Is there any solution to make the msi not to repair an installation ?
Sincerely
Sébastien Ros
James - 01 Oct 2004 22:31 GMT
This happens when a file that the msi installs is modified by the UAB. To
keep this from happening you need to edit your msi file with Orca and remove
the "KeyPath" value from the "Component" table for all of the files that you
will modify with the UAB. I've written more about this on the GotDotNet user
group.
> I made a smart client application with automatic updates throught version
> numbers. This application is installed using a .msi file generated with a
[quoted text clipped - 8 lines]
> Sincerely
> Sébastien Ros