0

I created a patch (MSP package) that mainly updates the executable of the application. As a test I tried running the patch when the executable is running. Strangely, enough the executable was replaced. I.e. windows normally doesn't allow to modify the EXE file that has an open handle to it. How does Windows Installer handle it? I know about the trick with renaming the executable and placing another one instead but how does msiexec handle this and is it described anywhere (I looked through the docs but can't find it)? I'd appreciate any replies as I'm mainly interested how reliable this behavior is.

Thanks!

user1552175
  • 178
  • 10
  • What application if I may ask are you referring to here? – Chelseawillrecover Nov 11 '13 at 22:31
  • Most likely the restart manager handles this for you: http://msdn.microsoft.com/en-us/library/windows/desktop/aa373524(v=vs.85).aspx – Bogdan Mitrache Nov 12 '13 at 08:01
  • @Chelseawillrecover: it's an executable I built that is installed and patched using Windows Installer – user1552175 Nov 13 '13 at 10:30
  • @BogdanMitrache: the point is my executable is not restarted, it runs normally but its contents and size change after the patch is applied (but no restart of the system or my executable ever happens at all). – user1552175 Nov 13 '13 at 10:31

0 Answers0