Note that there are some explanatory texts on larger screens.

plurals
  1. POWiX Toolkit, MSI product with bootstrapper bundle, what is the correct sequence of events?
    primarykey
    data
    text
    <p>My application requires 12 DLL files and <a href="http://en.wikipedia.org/wiki/.NET_Framework" rel="nofollow">.NET</a> 4.0 Client profile and <a href="http://en.wikipedia.org/wiki/SQL_Server_Compact" rel="nofollow">SQL Server Compact</a>. </p> <p>Using WiX Toolkit 3.7 and <a href="http://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Visual_Studio_2012" rel="nofollow">Visual Studio 2012</a>, I have built a <a href="http://en.wikipedia.org/wiki/WiX#Burn" rel="nofollow">Burn</a> bootstrapper that installs the .NET 4.0 and SQL Server Compact and then my MSI file which has all the DLL files, etc. I did this by reading the documentation and other questions on Stack&nbsp;Overflow regarding Wix. I'm testing the install process on a freshly installed Windows 7 machine. :)</p> <p>However, I am confused about one aspect of the installer process...</p> <p>I thought that my MSI file ran as the primary installer and only if .NET 4.0 CP or SQL Server Compact were missing on the target machine only then the bootstrapper would fire up and install the missing packages.</p> <p>The situation I have now, while it works, is that my MSI file is hidden and the only file I have is my <code>Bootstrapper.exe</code> file and the only dialogue I see during install is the bootstrapper dialogue. Is this correct or am I doing something in a bad way?</p> <p>I have changed the build output of the Bootstrapper to MSI, so I am left with a single MSI file which is great. Considering the fact that the original <code>product.wxs</code> project output (MSI file) is now embedded in the <code>Bootstrapper.msi</code> file - should I take all the UI elements out of the original product.wxs project?</p> <p>If so, I'm guessing I can customise the bootstrapper UI.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload