I just installed WiX 3.5.1512.0 onto my build server and added a new project
that is using WiX to the build. I am getting strange behavior when compiling
my installer. I don't see any build errors, and the MSI does get built but
it is put in the wrong path. When building my release configuration the MSI
is output into the following directory:


MyProject\`, `bin\Release\`))`))MyProject.msi\


*NOTE*: the backticks, commas, and extra parens.

This project is developed in VS2010 but targeting .NET 3.5.  I narrowed the
problem down to the WiX2010.targets file on the build server (C:\Program
Files\MSBuild\Microsoft\WiX\v3.5\wix2010.targets)

In that file I found the following property group

<PropertyGroup>
    <!-- Example, c:\MyProjects\MySetup\bin\debug\ -->
    <!--
    Condition intentionally omitted on this one, because it causes problems
    when we pick up the value of an environment variable named TargetDir
    -->
*    <TargetDir Condition="'$(OutDir)' !=
''">$([System.IO.Path]::GetFullPath(`$([System.IO.Path]::Combine(`$(MSBuildProjectDirectory)`,
`$(OutDir)`))`))</TargetDir>
*
    <!-- Example, C:\MyProjects\MySetup\bin\debug\MySetup.msi -->
    <TargetPath Condition=" '$(TargetPath)' == ''
">$(TargetDir)$(TargetFileName)</TargetPath>

    <TargetPdbPath Condition=" '$(TargetPdbPath)' == ''
">$(TargetDir)$(TargetPdbName)</TargetPdbPath>
  </PropertyGroup>


*NOTE:* the escape sequence in the $(OutDir) condition. Also note the
comment above stating the condition is intentionally omitted, However it
isn't actually commented out. Either the comment is out of date or this
condition should actually be commented out?

The code snippet in the condition looks like powershell to me so I thought
maybe it was a version issue with powershell on my build server causing the
problem? I upgraded to powershell 2.0 on the server and it didn't fix the
problem.


Builds work correctly on my dev box (Win 7 x86 Enterprise). I am stumped at
this point what is causing the issue?

Any ideas?


Thanks




Brad Cunningham
Microsoft MVP: C#

http://blog.bradcunningham.net
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to