For those like me (I never used Windows) who do not know WiX; https://wixtoolset.org/. - Source: Hacker News / 2 months ago
I actually like WiX[1] — it has a bit of a learning curve, but, so long as I'm building on Windows and don't stray far from the default UI flows, I haven't found an easier tool for creating Windows installers as part of a product build process, especially those that require Windows-specific bits like COM component registration, Windows service management, setting restrictive ACLs on installed components, etc. And... - Source: Hacker News / about 1 year ago
For Windows, in the past, I’ve used the WiX toolset to create installers (https://wixtoolset.org/). Source: about 1 year ago
Https://wixtoolset.org/ should be able to help you out there. Source: about 1 year ago
For windows - store: https://developer.microsoft.com/en-us/microsoft-store/register/ - requirements: https://learn.microsoft.com/en-us/windows/apps/publish/publish-your-app/app-package-requirements?pivots=store-installer-msix - alternatively you can make MSIs and distribute them through your own website or another service. https://wixtoolset.org/ - publishing with chocolatey isn't a terrible option to help users... Source: over 1 year ago
The ones I know of are WiX[0] and NSIS[1]. 0: https://wixtoolset.org/ 1: https://nsis.sourceforge.io/Main_Page. - Source: Hacker News / over 1 year ago
Https://wixtoolset.org/ Dont need anything else :). Source: over 1 year ago
The Wix Toolset, which makes msi installers, is probably overkill, but once you get it setup, it works pretty well. I use the command line tools and don't bother with the VS plugins. I found this guide helpful for setting up the wxs files. Source: over 1 year ago
Not sure what you are talking about. The game uses a basic MSI installer built using Wix toolset and definitely doesnt install anything to your kernel. Its an exe that runs dot net core, which isnt even core that can run inside the kernel. Source: over 1 year ago
It's an awesome installer, I used it in the past. If a person knows any scripting language at all, I think they will create an installer with NSIS in less than a day of work. Still, for commercial-quality software I prefer my installers to be declarative, not scriptable. With a scriptable one, it's easy to leave installed files after uninstalling, break things when an installer fails near the end, or even... - Source: Hacker News / over 1 year ago
In regards to Open With, I use WiX Installer (not the stupid web site host/editor) and this is handled during install. Sample is here: https://stackoverflow.com/questions/2772452/how-to-associate-application-with-existing-file-types-using-wix-installer. Source: over 1 year ago
It depends on what you mean by "install" exactly. If you want to appear in the windows installed program list, then chocolately, scoop, winget, or building your own MSI are the way to go (WIX, or other more modern or paid tools...but be warned this is complex). If you just want them to be able to run it (and in the %PATH%) then a simple copy operation is sufficient with perhaps a command-line option to add itself... Source: almost 2 years ago
It ain't pretty and takes a while to get used to, but in the past I've used WiX: https://wixtoolset.org/. Source: almost 2 years ago
While Microsoft's WiX system for building MSI installers does have an open-source cross-building implementation for POSIX platforms in the form of msitools (Note that wixl is split out into a separate package on Debian-family distros), the documentation for WiX Toolset reminds me of the early years that made Git infamous. Source: almost 2 years ago
If you really want to bundle a compiler, my advice would be to just use an installer like Inno Setup or NSIS or the WiX Toolset via WixSharp and have it either download or bundle the installer for the compiler. Source: about 2 years ago
I didn't get this one and had to look it up, because I thought "Wix" was still an MSI authoring toolset ;-). Source: about 2 years ago
I'm thinking of .msi files on Windows and .pkg or .dmg files on Mac. I would like to understand the file structure of these installers and how to construct the installers using the most basic tools possible instead of relying on things like WiX (https://wixtoolset.org/). If I could automate the installer production using CMake, that would be even better. Source: about 2 years ago
One way might be to use WiX - http://wixtoolset.org/. You can embed the EXE in the MSI and have it quietly run the contained exe. Some reference material: http://wixtoolset.org/documentation/manual/v3/customactions/qtexec.html but it would just author some XML, same it as example.wxs and run: Candle example.wxs Light example.wixobj -ext WixUtilExtension This will generate an MSI. Source: over 2 years ago
I've used the WiX toolset as a fairly easy way to create msi installers. You define a folder path, files to live in that folder, and can also define short-cuts. WiX will compile your files into a msi file which you can then use for install, uninstall and upgrades. Source: over 2 years ago
Use https://wixtoolset.org/ to create a msi and deploy via MDM or group policy. Using ServiceInstall in wix works very well. Upgrades will automatically stop, upgrade, start it again. Source: over 2 years ago
You can try out the wixtoolset https://wixtoolset.org/ for more complex MSI installs. Source: over 2 years ago
Do you know an article comparing WiX (Windows Installer XML) to other products?
Suggest a link to a post with product alternatives.
This is an informative page about WiX (Windows Installer XML). You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.