I have figured out why this is happening. With the WiX installer being compiled on a x86 platform, Windows 7 picked it up as the 32-bit installer with 32-bit registry keys. Windows 7 64-bit handles 32-bit registry entries by doing just what I saw happening. The program was still registered; it was just not in the … Read more
Well, there is the free way and the $$$ way. I cannot document everything here, but this should get you started. On a side note, yes, Windows Installer is a maddening technology. There are many times where I think a task will be straightforward, but it actually becomes complicated. You definitely have to immerse yourself … Read more
I figured out how to add Custom Prerequisites to the Visual Studio prerequisites dialog box. MSDN as a good article on creating the prerequisite. Basically you just have to create a product manifest and a package manifest, copy them along with your distributable file to : \Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages. Visual studio will automatically pick it … Read more
If you want to use WiX, you need at least a basic understanding of how Windows Installer works. The best reference around is The Definitive Guide to Windows Installer, which runs through the all basics with examples using Visual Studio and Orca. WiX is very easy to learn once you understand Windows Installer. A properly … Read more
Better for the way you go might be the AfterInstall parameter. The following script will execute the RunOtherInstaller function right after the OtherInstaller.exe file entry is processed. There it tries to execute the just installed OtherInstaller.exe file and if that fails, it reports an error message to the user. Please note that you cannot interrupt … Read more
CMake sets the boolean variable CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT if CMAKE_INSTALL_PREFIX has not been explicitly specified and is initialized to its default setting. You can override it in the following way: if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT) set (CMAKE_INSTALL_PREFIX “${CMAKE_BINARY_DIR}/installed” CACHE PATH “default install path” FORCE) endif()
Are you running on Windows or Linux? If so, fsevents cannot be installed, as it is an OSX-only package. If you run npm with –loglevel=error, you should no longer see this or any other warnings. As far as I know, there is no way to selectively suppress warnings in npm.
For those using Chocolatey (this is not published on the website yet, but found the info in the github repo): Watchman is available to install via the Chocolatey Windows package manager. Installation is as simple as: PS C:\> choco install watchman Reference: https://github.com/facebook/watchman/blob/573b18b86b88759f31e83fa2e1837539d138de22/website/_docs/install.markdown#installing-on-windows-via-chocolatey Beware that installing Chocolatey itself is somewhat tedious, but here is the … Read more
Windows Installer (MSI) uses the following command line arguments to be silent: Silent install or silent major upgrade: msiexec.exe /i foo.msi /qn Silent minor upgrade: msiexec.exe /i foo.msi REINSTALL=ALL REINSTALLMODE=vomus /qn Silent uninstall: msiexec.exe /x foo.msi /qn Executable path: C:\Windows\system32\msiexec.exe