by this.
From: Rob Mensching r...@robmensching.com
Sent: Friday, December 28, 2012 10:46 PM
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Transition from InstallShield to WiX
Easiest way is to use dark to decompile your MSI
I was wondering: are there many big microsoft softwares that uses WiX
with burn?
On 29/12/2012 05:43, Rob Mensching wrote:
Easiest way is to use dark to decompile your MSI. Burn (the WiX toolset
bootstrapper) creates Bundles that can install prerequisites and far more.
For example, the
Visualt Studio and Windows SDK are two that I know about off the top of my
head. WiX v3.6 is still relatively young so I expect more will show in time.
On Sat, Dec 29, 2012 at 5:32 AM, up2date.cyb...@gmail.com
up2date.cyb...@gmail.com wrote:
I was wondering: are there many big microsoft
On 29/12/2012 14:12, Rob Mensching wrote:
Visualt Studio and Windows SDK are two that I know about off the top of my
head. WiX v3.6 is still relatively young so I expect more will show in time.
Also the Windows Driver Kit 8.0. The WDF CoInstaller package is just a
plain WiX msi (with the red
Can anyone point me to a web resource that would ease the transition from
InstallShield to WiX?
I've been using DTF for several years writing custom actions for
InstallShield. I'm interesting in giving the rest of WiX a try.
I'm specifically confused about the Wix bootstrapper and how it is
Easiest way is to use dark to decompile your MSI. Burn (the WiX toolset
bootstrapper) creates Bundles that can install prerequisites and far more.
For example, the Visual Studio install (~130 packages) uses Burn to install.
On Fri, Dec 28, 2012 at 2:40 PM, Richard J Otter r...@columbia.edu
6 matches
Mail list logo
