[wix-users] Could not harvest data from a file that was expected to be an assembly

[Ingmar]

Hi there,

 

I have problems building my first setup for a solution which uses prism. My
Product.wxs looks like

 

<?xml version="1.0" encoding="UTF-8"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">

  <Product Id="*" Name="TestSetup" Language="1033" Version="1.0.0.0"
Manufacturer="none" UpgradeCode="614eb7e3-e52c-4060-8999-5369fb8aa59d">

    <Package InstallerVersion="200" Compressed="yes"
InstallScope="perMachine" Manufacturer="none" />

    

    <MajorUpgrade DowngradeErrorMessage="A newer version of [ProductName] is
already installed." />

    <MediaTemplate EmbedCab="yes" />

    

    <Feature Id="ProductFeature" Title="TestSetup" Level="1">

      <ComponentGroupRef Id="ProductComponents" />

    </Feature>

   <UIRef Id="WixUI_Minimal"/>

  </Product>

  

  <Fragment>

    <Directory Id="TARGETDIR" Name="SourceDir">

      <Directory Id="ProgramFilesFolder">

        <Directory Id="INSTALLFOLDER" Name="next-office" />

      </Directory>

    </Directory>

  </Fragment>

  

  <Fragment>

    <ComponentGroup Id="ProductComponents" Directory="INSTALLFOLDER">

      <Component Id="ProductComponent"
Guid="{A5B56773-5E26-4C5F-AC51-C2470C3658AF}">

        <File Source="$(var.MyProject.TargetPath)" KeyPath="yes" />

     </Component>

    </ComponentGroup>

  </Fragment>

</Wix>

 

When building the setup project I get these error

 

Could not harvest data from a file that was expected to be an assembly:
Microsoft.Practices.Unity.dll

The file or assembly "Microsoft.Practices.ServiceLocation, Version=1.3.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" or a dependency was not
found

 

Could not harvest data from a file that was expected to be an assembly:
Prism.Wpf.dll

The file or assembly "Microsoft.Practices.ServiceLocation, Version=1.3.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" or a dependency was not
found

 

 

I don't know why Microsoft.Practices.ServiceLocation is missing, the
solution itself can be build and tested without any erros.

 

Anyone knows how I can fix this problem?

 

Thanks

 

Ingmar