Setting PathVariables with MSBuild and Tfs

[SirClutzz]

Hi All,

I am trying to set the PathVariables setting when using the InstallShield build task with MSBuild and TFS, and it will not set the value. I'm not sure if this is a bug, or I am doing something wrong (have not been able to find very much helpful documentation, like with examples)

I create a ItemGroup for the Path Variables like this:
<ItemGroup>
<InstallShieldPathVariables Include="$(DropLocation)\$(BuildNumber)">
<PathVariable>PATH_TO_APPLICATION BUI_FILES</PathVariable>
</InstallShieldPathVariables>
</ItemGroup>

And then use this like this:

<InstallShield InstallShieldPath="$(InstallShieldPath)"
Project="$(InstallShieldProject)"
ProductConfiguration="$(InstallShieldProductConfiguration)"
ReleaseConfiguration="$(InstallShieldRelease)"
OutDir="$(DropLocation)\$(BuildNumber)"
ReleaseFlags="$(InstallShieldReleaseFlags)"
PathVariables="@(InstallShieldPathVariables)"
OutputGroups="$(TaggedOutputs)"
MergeModulePath="@(MergeModulePath)"
Disk1Folder="$(DropLocation)\$(BuildNumber)"
BuildCompressed="true"
/>

Is this correct? The MergeModulePath does not seem to work either, but have read that that is a bug, so have given up on having my merge modules on a centalized network drive.

Thank you
SirClutzz

[Christopher Painter]

Between me and you, I'm not a fan of consuming build files directly from a network share. I always wire my build automation to copy everything local into a subdirectory off of the solutionroot directory and reference it from there.

[SirClutzz]

Thats pretty much what I have done, but my main issue is the path variable thing. The executables that need to be packaged are build as the first step of the build process, and the second step builds the installer using those executables, but it just doesn't work. Have I got the syntax right? Do you have any examples of how you have used this variable of the build task?

Thanks
SirClutzz