-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use WiX Toolset instead of NSIS #8
Comments
Thank you for the suggestion. What would be the advantage of using WiX over NSIS, besides WiX being "official"? From what I read online, WiX seems to be more difficult to use. |
Windows Installer (MSI) creates database driven, transactional installation packages. When written properly a Windows Installer package is very robust, a file gets corrupted/deleted and it will be automatically reinstalled. Windows Installer is aware of UAC and only elevates when required, basically if you're creating software for the corporate market, you will need to provide an MSI. If comparing to Linux, basically NSIS is creating a .tar.gz package with a binary and some system checks and WiX creates deb/rpm which can check installed libraries and other needed settings. |
Thank you for the clarification. I appreciate your reply, but must admit I'm sceptical about the very strong statement that "if you're creating software for the corporate market, you will need to provide an MSI". Chrome for Enterprise does offer an MSI installer. But Dropbox for Enterprise seems to use a simple .exe. Also Total Commander, which my file manager competes with, only offers an .exe and is installed on many machines world wide, including inside banks. So is it really that an MSI installer is absolutely, positively required? |
In order to use the built-in "Software Installation" Group Policy, you need to have an MSI package ready for deployment. EXE files cannot be deployed using Software Installation. It's just making sysadmin's job easier. |
(Good news for Linux CI) It seems it could be easily used on Linux also: https://packages.ubuntu.com/eoan/wixl |
The official way for creating installers for Windows is WiX Toolset. Could NSIS be replaced with it?
The text was updated successfully, but these errors were encountered: