Go Back
1 Vote

SDI Installer Should Inform Why A Reboot Was Required

User-added image

Restarting is a very expensive Context Switch (https://en.wikipedia.org/wiki/Context_switch) for our Developers. Most attempt to avoid rebooting whenever possible. It would be nice to have the installer tell us why it feels we need to restart the system.

In addition, whenever possible, reboots should be avoided or at least warning BEFORE the install completes (this dialog is only present after an install has COMPLETED).

1 Comment | Posted by Ace Olszowka to Visual Studio Integration, Installation on 8/29/2019 5:02 PM
Marty Lewis
Most of the time we do not have sufficient information at installation time to inform you why the restart is required. The information that is presented in the installation log is typically more complete than the information available to our bootstrapper or MSI implementations.

Synergex endeavors to meet the Microsoft Windows Logo standards when designing installations. One of the requirements is that our components and service registrations should not require restarts. To my knowledge, none of the installation components that we produce will require a Windows restart to complete.

However, I cannot speak for components from other vendors. From experience, the component that typically causes restarts during our installation is Microsoft's vcredist. We used to distribute this piece as a Merge Module inside of our MSI. We have since transitioned to utilizing Microsoft's vcredist executable at the bootstrapper level to help mitigate restart potential even further.

12/10/2019 8:40 PM   0  
Please log in to comment on this idea.