I think my case is a little different since it is a .NET application and we
have some third party dlls that don’t work on a 64-bit machine, so I just
switch that component so they don’t install on the 64-bit machine. I don’t know
when it is required specifically mark the package or components as 64-bit. I’ll
need to do some more testing myself as well to verify it does work. Another
option you could do though to reduce code duplication, is to separate all the
differences in the WiX into a fragment and have a 64-bit and 32-bit fragment
and just link in the appropriate on for each build. You’ll still have 2 msi’s
but less room for error.
-Matthew Rowan
From: Robert Randall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 7 February 2007 04:47
To: 'Matthew Rowan'
Subject: RE: x86 and x64 in same wxs / msi ?
Thanks. Does this allow you to have a single .msi file / database that can be
used to install on multiple target OSes, both AMD64 and x86? I posted a
similar question to a Microsoft list and received a “can’t do it” answer. That
answer does feel wrong. Do you use a single .msi for installs to x86 and x64
targets?
Thanks,
Robert.
From: Matthew Rowan [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 7:10 PM
To: Robert Randall
Subject: x86 and x64 in same wxs / msi ?
Hi Robert,
What I have done is just setup conditions on the platform specific components
to install or not dependent on the operating system.
eg.
<Component Id="Comp" DiskId="1" Guid="xxxxx-3FD7-4DB0-9BBC-2FDF305DE466">
<!-- Do not install on 64-Bit Windows -->
<Condition>NOT VersionNT64</Condition>
<File Id="file1.dll" Source="..\file1.dll" />
</Component>
Regards,
-Matthew Rowan
On 2/6/07, Robert Randall <[EMAIL PROTECTED] > wrote:
The answer to this may be obvious, but I can't seem to find any direction on
how to support multiple target OSes from the same package; say x86 and x64
(AMD64) versions.
My hunch is there is a simple answer but I've not been able to find a sample
project or How-To for this.
Would one of the experts please advise on how to best handle this? I have
two separate and nearly identical packages now that produce two .msi files.
One for x86 and one for x64. I would prefer to have a single package (less
room for mistakes that way).
Thanks.
Robert Randall
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk
<http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642>
&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
