Robert O'Brien wrote:
Regarding response to q1 - after sending mail I saw the following
comment on http://wix.sourceforge.net/. Is that comment suggesting
that fragments are still valid and the recommended way for breaking
apart a wxs development project but now the element name used to
reference those fragments has changed and the scope of what they
contain is defined by how they are referenced?
FragmentRefs were dropped in favor of the strongly-typed *Ref elements.
Regarding response to q2 -- Using the <?if?> flag and
$(var.variables) preprocessor references will impact the results of my
msi output at compile time based on the host I used to compile versus
what happens at msi runtime during installation right?
No, based on the flags that you pass in. For example, you can use a
Platform preprocessor variable and use it in <?if>s if you need
platform-specific authoring.
Is creating x64 and x86 specific msi build output the current
recommended approach versus a single msi that at runtime can handle
x64 and x86 installation differences?
MSI doesn't support having one .msi package that supports both 32-bit
and 64-bit components.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
