Advertised shortcuts don't cause repair to be unavailable, just the
part that is associated with advertised shortcuts repairing the
containing feature if a component is missing. In that sense it's not a
product repair, just a feature repair. There's always manual repair if
something does get remove
I have large DVD size setups authored in Installscript, which I am converting
to wix. I have moved most of the applications to individual msi packages,
batch built in seven languages, with external cabs. These packages are used
in multiple bundles for different types of product configurations (cl
> El 03/11/2014, a las 12:15, Phill Hogland escribió:
>
> Would it be a better approach to define a wixlib for the 'library' files and
> use the wixlib in each msi package which requires the library, so that each
> msi package is atomic from msi's perspective? Then on-demand install of
> advert
Would it be a better approach to define a wixlib for the 'library' files and
use the wixlib in each msi package which requires the library, so that each
msi package is atomic from msi's perspective? Then on-demand install of
advertised features would be complete.
--
View this message in contex
colas.alva...@gmail.com]
Sent: Sunday, November 2, 2014 4:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Advertised shortcuts and the new world of bundles
If I have a single .msi that installs files and an advertised start menu
shortcut, and some files become
If I have a single .msi that installs files and an advertised start
menu shortcut, and some files become damaged or missing, launching the
start menu shortcut will repair the relevant feature(s) and launch the
application anyway.
But let's say I have a Burn bundle with two .msi's, one with require
6 matches
Mail list logo
