I've tried to understand what you are describing...
It sounds to me, like a "Repair" from the installer should be run before the
second execution of the application. I would think this happens
automaitically if the files are marked "critical" in the setup program.
[quoted text, click to view] "Lamrin" wrote:
> Here's the context. We have a setup program that will deploy an application
> to our clients. The exe deletes all of its files when the user exists from
> the application (I know this is odd, it's a requirement of the project). To
> run the application again, the user must run the msi twice. The first time
> to remove the previously installed application. The second time to install
> the application again.
>
> In the setup project I've set the RemovePreviousVersions property to True.
> In this context, the msi will actually do a silent unstall before the
> reinstall as long as the version number of the setup project has been
> incremented. How can I replicate this same behavior (silent uninstall then
> reinstall) without incrementing the version number of the setup project?
>
> Seems like CustomActions might be a possible solution. Has anyone had any
> similar experiences?
>
