I'm creating a custom UI using the Wix 3.6 BootstrapperApplication and have
a working installer using the windows installer system. However, we'd like
to give the user the option of performing an "xcopy" style install instead
of fully registering via the windows add/remove programs, etc. This is
particularly useful when users/devs want to have side-by-side installations.
To achieve this, if the user selects the xcopy option, I'd like to be able
to use the same .msi files and do something like this:
if (UseXcopy)
{
var package = new
Microsoft.Deployment.WindowsInstaller.Package.InstallPackage(package.LocalSource,
DatabaseOpenMode.ReadOnly);
package.WorkingDirectory = _LayoutDirectory;
package.ExtractFiles();
}
I'd then just skip the call to Engine.Apply(), thus bypassing the MSI
installers.
However, I haven't found a way to get access to the msi path/files for my
packages. In my case, I have multiple MSI files chained in my bundle. I've
found the WixBundleOriginalSource variable, but that just gives me the .exe
file, and, from what I can tell, can't be used with the InstallPackage,
etc, classes.
So my questions are:
Is there a way to get the MSI files at install time (wouldn't need them for
upgrade/repair, etc, just install)?
Is there an alternative approach to getting this xcopy-style install
without writing a second installer?
thanks
~John
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
