trioan.blogg.se

1. Graw extract bundle files how to#
2. Graw extract bundle files .exe#
3. Graw extract bundle files install#
4. Graw extract bundle files update#
5. Graw extract bundle files full#

I do this in SetEngineVarsInSession by copying the properties I want from the Bootstrapper's StringVariable. You also need to set the Properties for the session. Make sure to store the old UI level so you can restore it when you're done. I also set the UI level to Silent to prevent the MSI's UI from showing. This is done using the OpenPackage method - but we need to tell it to ignoreMachineState, otherwise it will look for this MSI in the system registry and get all confused. Since we'll basically be using MSI/WiX to "install" these files, and they require a Session to run, we need to create our own session object. I do this in the UpdateMSIFeatureTableToSetInstallableFeatures method by changing the Level value in the Feature table. Otherwise, we need to modify the level values in the MSI's database to change it to 1 for those features we want and to something higher than 1 for the features we don't.

Graw extract bundle files install#

So if all you want to install is the Level 1 features, you can skip this step. Anything that's a Level 1 will be installed. step 2b: set the installable features in the MSI databaseĪs I mentioned above, the Level value for each feature determines if it's installed by default of not. I do this in the UpdateMSIDirectoryTableToUseNewApplicationFolder method by changing the DefaultDir value in the Directory table. The way I achieve this is by setting it to "." (the current folder), which will override everything above it in the folder hierarchy as well. So I need to change the location of this folder in the MSI database to allow me to install somewhere other than Program Files. All of my files get installed at or below this level.

Note that I have a top-level folder APPLICATIONFOLDER defined just under the ProgramFilesFolder. wix files, you should have defined a bunch of Directory targets, like this:

Graw extract bundle files update#

The first thing we need to do is update the install folder. step 2a: set the install location in the MSI database So we'll interact with the database using SQL statements in order to change the behavior of the installer. Keep in mind, the MSI package is basically just a database with the files embedded. To do this, I used the WiX InstallPackage class, which wraps our MSI package. Now, we loop through each of the MSIs you want to install and use the InstallPackage method to actually extract the files from them into your target folder. This throws the MSI files into a AttachedContainer subfolder of our temp working folder. This is actually pretty straightforward using the WiX Unbinder class.

Graw extract bundle files .exe#

exe and place them into a temporary working folder. The ExtractComponentInstallersFromBundle method is used to extract the. Here's a high-level overview of what happens: Step 1: extract MSIs from bundle Then RunInstall() and watch the magic happen. Using my MsiFileExtractor class, you'll need to pass into the cxtr the target folder where you want the files extracted into, the list of features to be installed for each MSI, and a reference to the MBA object itself. I'm assuming you don't just want to install the defaults and that you want to select which specific features to install.

Graw extract bundle files full#

I do this all through a class I call MsiFileExtractor - the full source is at the end of this posting, so I'll walk through the methods a little at a time.įirst, you need to know a couple of things (which I've put into the cxtr):

Graw extract bundle files how to#

It does not run any of the CustomActions (I'll post how to do that later). msi by using the WiX SDK.īelow is a walkthrough of just extracting the files and laying them down on the filesystem. msi from your bundle while it's running if you're using a custom bootstrapper application, then extract the contents of that.