1 reply to this topic

[smc0862]

I've written a new Basic MSI project that works fine during a clean install, but now I need to get it working when installing on top of an older version of our product that was deployed using InstallShield 5.5. For the most part, it's working fine, but now I'm running into a situation where files are not being updated due to the older application running and locking them. I was hoping MSI would detect this and update the files on reboot. I didn't see any way of marking the file as potentially locked.

Is there a way to make MSI aware of these applications so that it will complain during the ValidateInstall action and throw up the FilesInUse dialog? Is there a table I can add these to?

Thanks,

-Shawn

[Stefan Krueger]

This should happen automatically, no additional settings needed. generate a log to see what's going on.