I think I found the answer. By using Popen with close_fds = True I was able to start up a process that was independent and without handles to the parent. For docs look here and search for close_fds. Or, on Windows, if close_fds is true then no handles will be inherited by the child process. … 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
“Reference-Style” Answer: This is an alternative answer to the one below with several different options shown. Uninstalling an MSI file from the command line without using msiexec. The command you specify is correct: msiexec /x {A4BFF20C-A21E-4720-88E5-79D5A5AEB2E8} If you get “This action is only valid for products that are currently installed” you have used an unrecognized … Read more
Go into cmd(command prompt) or the run dialog (Windows + R) and execute msiexec -?. It will open a window containing your version at the top.
Try to change the GUID of the components which are not uninstalling. I tried the same and it worked for me. It may be because the GUID is already registered in the registry by some other product. The cause is generally messed up component reference count in the registry – often it happens on dev-boxes … Read more
Unfortunately, No. NSIS lets you create scriptable, procedural installation packages. It’s simple, easy to use and has a number of features not present in Windows Installer. 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. … Read more
You can find a solution here To quote: The problem is that the MSI infrastructure is looking for the installation state file which is usually created during the Install phase. If the custom action does not participate in the Install phase, no file is created. The solution is to add the custom action to both … Read more
This must be helpful. Pay special attention to the bottom of the page, a guideline of 2 steps how to pass values via CustomActionData. Here is the excerpt: To write the value of a property into the installation script for use during a deferred execution custom action: Insert a small custom action into the installation … Read more
You could update the OutputName of your .wixproj and use an MSBuild variable to pass through the version number or any other variable you like. My build script looks like this: set PRODUCTVERSION=7.1.0.1 MSBuild.exe /p:Configuration=Debug /p:ProductVersion=%PRODUCTVERSION% Installer.wixproj And my WiX project looks like this: <?xml version=”1.0″ encoding=”utf-8″?> <Project ToolsVersion=”4.0″ DefaultTargets=”Build” xmlns=”http://schemas.microsoft.com/developer/msbuild/2003″> <PropertyGroup> <Configuration Condition=” ‘$(Configuration)’ … Read more
Thanks for all the suggestions! After much trial and error the real problem here seems to be the Visual Studio 2008 Setup Project – manually setting up a link to my executable correctly uses the high resolution icon, however the link that is created by the setup doesn’t use the correct icon. When setting the … Read more