wix3.6

I am using Burn for MSIs package. I am using Votive (Visual Studio) & my own custom BA instead of WiXBA. I tried to debug custom BA using Debugger.Launch() . But when I start debugging, error messages occur. No symbols are loaded for any call stack frame. The source code cannot be displayed I realized that package.exe links CustomBA dll which located at C:\Documents and Settings\user\Local Settings\Temp\{GUID}\ . {GUID} is always changed. So, whenever I run package.exe, always directory is changed. I think that is the reason to occur errors. In Visual Studio, When I started package.exe with

How do I reference the RebootPending property in a Burn (WiX) bootstrapper? I know the property name is RebootPending, which is actually referencing the MsiSystemRebootPending property in Windows Installer. I'm currently trying something like this: <bal:Condition Message="There is a restart pending. Please restart your computer before attempting to install !(loc.ProductName).">RebootPending = 0</bal:Condition> But it's always true, even when Windows Update has just finished an update and needs to restart. Is my syntax wrong? Should my condition have [RebootPending] instead? Having been

I am using <MajorUpgrade> in WiX 3.6 to force an uninstall of the previous version of my application when installing a newer version. My application installs an extension DLL file into Windows Explorer, so on uninstall the Files In Use lists Explorer and defaults to shutting down the listed application. This does kill Windows Explorer as my shell goes away (which is somewhat jarring for the user), however I still get an error saying that not all applications could be shutdown and states a reboot will be necessary. My preference is to avoid this thrash and skip the Files-In-Use dialog just

I have a WIX_bundle (V1.0.0.0) which installs 4 third party MSI's of the version (5.0.0.0). Now the new version of my third party MSI's got updated (6.0.0.0). I created a new version of the WIX_Bundle with (v2.0.0.0) and both the WIX bundles have the same upgrade code. What I want to happen is that the new version of the WIX_Bundle should uninstall the previous version (v1.0.0.0 along with the 4 MSI's) and install the new version (v2.0.0.0 with new 4 MSI's). But when I try to install the WIX_BUndle V2.0.0.0, it tries to install the new version and is not doing an uninstall of the previous

I want my install to fail if a third-party software element is not installed. I added a Fragment with a util:RegistrySearch and a bal:Condition to the Bundle , but I can't get it to work. ThirdPartyCOMLibraryInstalled never evaluates to true. I've confirmed that the key exists, and the value I use for Key is correct - I copy/pasted the name from the selected key in regedit. There aren't any errors in the log. I'm building the installer with WiXTools 3.7 in Visual Studio 2012 on Windows 7 64-bit and testing on both Windows XP SP3 and Windows 7 64-bit. Searching online for other examples for

Is it possible to somehow unpack a bundle? I need to make sure all packages within a bundle are signed correctly... TIA Dark.exe decompiles bundles; use -x to extract the bits. Run the installer with the argument -layout and it should download or extract (as appropriate) the packages that it contains to the directory the installer is in. You can specify a target directory as a second argument if you wish. This was tested with a bundle created with version 3.6.2520.0 . It is known to be broken on the current weekly release of wix36.exe itself. insignia will extract the engine. insignia -ib