Hi,
When I add a reference to WixUtilExtension in my WiX project, this is what
gets added to the .wixproj:
<ItemGroup>
<WixExtension Include="WixUtilExtension">
<HintPath>$(WixExtDir)\WixUtilExtension.dll</HintPath>
<Name>WixUtilExtension</Name>
</WixExtension>
</ItemGroup>
When my colleague does this, he sometimes gets the above, but usually gets
this:
<ItemGroup>
<WixExtension Include="WixUtilExtension">
<HintPath>
..\..\..\..\..\..\..\..\..\..\..\..\..\Program Files (x86)\WiX Toolset
v3.8\bin\WixUtilExtension.dll
</HintPath>
<Name>WixUtilExtension</Name>
</WixExtension>
</ItemGroup>
Which causes an error for me. Although we both have WiX 3.8 installed to
the default location (c:\Program Files (x86)\WiX Toolset v3.8) I have all
my source on a different drive, so that's where the relative path starts
from. Since there's no way that a relative path will ever be able to
reference a file on a different drive, it fails on my machine.
My colleague is having to check his project changes carefully to make sure
he doesn't accidentally break it, and we think the tools could help us
more. I'm pretty sure that in his case Votive is thinking "aha, I can draw
a relative path from here to there!" and just using that, while in my case
it's deciding it can't possibly do that so it's falling back on whatever
$(var.WixExtDir) tells it to do.
I found a bug (http://sourceforge.net/p/wix/bugs/2209/) on SourceForge, but
though it says "migrated" I was unable to find a bug on the new bug
tracking system. The closest I could find was this one :
http://wixtoolset.org/issues/2834/ but that's a totally separate issue. I
wonder if 2209 got lost along the way from SF to the new system. Should I
create it in the new system?
In terms of a fix, I feel like it should always use $(WixExtDir) regardless
of whether a relative path *could* be used.
Meanwhile, we have to decide how to handle it on our side until it's fixed.
We have tools that we could use to check this for us, but that's less than
ideal. We could also do what this guy does :
http://wixtoolset.org/issues/2834/ and keep our WiX toolset in source
control but for various reasons we didn't want to do that.
Any ideas?
Thanks
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
