q1 - In the new wix3 way patch msp generation xml is there a way to specify the
<PatchFamily> element to cover get the msp patch generated to cover changes to
all components from v1.0 to v1.1 versus having what appears to be the need to
specify every component explicitly as the patch help document sample syntax
suggests?
<Patch AllowRemoval="yes" Description="!(loc.ProductName)"
Manufacturer="!(loc.ProductName)" MoreInfoURL="!(loc.ProductUrl)"
Classification="Update" DisplayName="!(loc.ProductName)">
<Media Id="5000" Cabinet="Rtm.cab">
<PatchBaseline Id="Rtm" />
</Media>
<PatchFamilyRef Id="v11ReleasePatchFamily"/>
</Patch>
<Fragment>
<PatchFamily Id="v11ReleasePatchFamily" Version="1.0.0.0" Supersede="yes">
<ComponentRef Id="Service1" />
</PatchFamily>
</Fragment>
q2 - when a msp or msi minor upgrade is being processed do public property
settings that were defined during the v1.0 initial installation need to be
defined again for the minor upgrade processing or will the values specified
during v1.0 initial installation be reused, e.g. INSTALLDIR, MYSVCWEBSITENAME,
MYSVCWEBSITEPORT, MYSVCDATABASENAME, etc.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
