Those two dlls are part of the Expression Blend Studio (which I have very
little experience with).  However so far as I am aware, Visual Studio and
Blend are only deployed to 32 bit environments (x86 or WOW64) and the .Net
applications which consume those dlls should be compiled in Visual Studio as
AnyCPU.  So from a wix perspective there is no need for an installer which
targets x64.  A properly designed installer which targets
<InstallerPlatform>x86</InstallerPlatform> (which is the same as the default
with no InstallerPlatform property defined), should work on either a 32 bit
or 64 bit OS PC.

I am relatively new to wix and msi, so others have much more expertise than
I.  I find code generated by decompiling someone's setup to be very
difficult to understand, and probably not desirable to be 'modified' for use
as a shipping product.  From what I have read it is better to only specify
the attributes which are needed and leave the other stuff for the toolset to
manage.  So rather than code like this: 

          <Component Id="PartyPrintUtility"
Guid="{47D7C69E-81C2-4FD6-B77B-790FBF5F7B39}">
            <File Id="PartyPrintUtility.exe"
Source="$(var.SourceDir)\PartyPrintUtility.exe" KeyPath="yes"
Checksum="yes"/>
          </Component>
          <Component Id="cspstat.dll"
Guid="{69CAD367-A9D1-46E7-B8BA-CF839D034175}">
            <File Id="cspstat.dll" Source="$(var.SourceDir)\cspstat.dll"
KeyPath="yes" Checksum="yes"/>
          </Component>

In most cases all that is really needed is the following, except that in
some special situations it may be necessary to define a File Id or a
Component guid.  But so far for me those situations are rare.

<Fragment>
  <ComponentGroup Id="MyApplication" Directory="MyAppFolder" >
          <Component>
            <File Source="$(var.SourceDir)\PartyPrintUtility.exe"
KeyPath="yes" />
          </Component>
            <File  Source="$(var.SourceDir)\cspstat.dll" KeyPath="yes" />
          </Component>
  </ComponentGroup>
</Fragment>

Then a <ComponentGroupRef Id="MApplication" /> is added under the <Feature
...> element (along with other <ComponentGroupRef when describe the other
files).

You would also have a fragment that describes your directory tree similar to
the wix source code at src\Setup\CommonLib\Folders.wxs



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Making-64-bit-installer-from-32bit-wix-file-tp7593557p7593688.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to