I have modified code files in both the dotNetInstaller and InstallerEditor projects to add basic support for silent installs. The approach for adding such support was as follows:
* Addition of a "silent_install" property to the Bootstrapper XML
* Implementation techniques were chosen based on which approach was deemed to change lesser amounts of code
* At the present, a command line switch for performing silent installs has not been implemented. Because of the added "silent_install" property, end-users don't need to be concerned with command-line switches, but I can see where a command line switch feature might be of benefit to others. Such a feature should be able to leverage the changes already made in support of silent installs.
* Dialog boxes are bypassed if a silent_install is requested. If the dialog box is triggered due to an error or other unexpected condition, it is possible that the process that launched a dotNetInstaller setup exe may not know that there was a failure somewhere along the way. Perhaps an ErrorLevel bitmask could be used to signify various error states (similar to RoboCopy)?
The attached *.zip file contains only the files that were modified. Download the version 184.108.40.206 source, and then copy the contents of the attached zip over top the original source. I found WinDiff directory and file comparison to be helpful in viewing my changes against the original.
Disclaimer: I would like to emphasize that the modifications and testing were based on my current usage needs. In other words, I am not (yet) using all the features of dotNetInstaller, and while I have attempted to cover all potential areas, I may have missed a few things along the way. Nevertheless, I am posting this in the hope that it may be of benefit to the community and perhaps even be enhanced by others.
Log in to post a comment.