c# - wix: How to prevent user from restarting machine during the installation or upgrading of application -


there possibility machine shutdown/reboot/logoff when update\installation happening might corrupt install.

if have rollback option in place scheduling removeexistingproducts afterinstallinitialize, resume installation\update after machine restarts?

if there way in wix such can prevent user restarting , logging off during installation\upgrade?

how can make wix installer resumes remaining work after restart or after abrupt shutdown (via hardware)?

update

we have desktop application deployed our clients. there provision our client auto upgrade latest version. our application download latest version of msi , run msiexex.exe command in silent @ background user not have anything. things done silent @ background. working perfectly. now, of our client complains had v2.1 earlier has gone now. thinking following possible cases:

  1. during upgrade, latest version of msi downloaded , invoked using command msiexec.exe @ background application itself. uninstallation of installed (existing) version completed installation of new version gets failed leaving both versions uninstalled machine.

    as per reading different forums, appears rollback in wix occurs if there failure in uninstallation of existing version. so, question is: if there error during installation of new version, roll existing version?

  2. since user never know update of application going on done in silent mode, user may restart or shutdown machine in meantime of upgrade. so, initial question was: installation corrupted if machine restarted or shut down in middle of installation. said, if things in transactional , designed recover reboots @ time, us. so, mean not have handle such case ourselves? handled automatically wix?

so, case#1 cause application uninstalled during upgrade? or there other possibilities?

windows installer restarts after reboot fine, if reboot during installation phase. there forcereboot action force happen if install needs it, , there afterreboot property set detect if there reboot during installation.

if removeexistingproducts (rep) after installinitialize within transaction, , failure of upgrade result in rolling upgrade, , includes rolling rep , installing installed product. scenario many installs don't test, , failure reinstall product result in neither of products being installed. nothing reboots, it's rolling rep silent install of older product, requiring essential properties restored , custom actions behave properly. seems issue if clients find nothing installed after failed upgrade.

if rep after installfinalize outside transaction. means newer product installed, transaction finishes, old product uninstalled, , if fails you'll left both old , new products installed.

if using wix , bundles install or upgrade multiple msis there rollback boundary control how roll in series of msis.

again, doesn't matter if there reboot - windows installer can deal fine, , looks rollback failed reinstall original product. should upgrade taking complete verbose log (which imo should default if control command line , can add logging options). log should show failures during upgrade.


Comments

Popular posts from this blog

sequelize.js - Sequelize group by with association includes id -

android - Robolectric "INTERNET permission is required" -

java - Android raising EPERM (Operation not permitted) when attempting to send UDP packet after network connection -