Join GitHub today
Toolset Installer does not install in correct location for Build Tools #5700
Before marking this as duplicate, please note that I have seen issues #5622 and #5525. I don't believe that the suggested fix to the project templates fully fixes the issue on machines where only Build Tools (not Visual Studio) is installed.
Referenced in the above issues, the wix targets are imported from
When installed on a machine with a full VS installation (eg the professional version), this path resolves to
However, when only the bare Build Tools are installed (eg on a build server), the path resoves to
I have tried both the stable 220.127.116.111 installer as well as the 18.104.22.1682 weekly installer. Both seem to exhibit the same behavior. The build server is running Build Tools 2017 on Windows 7 and .Net 4.7 is the latest framework version installed.
Manually copying the files is the wrong thing to do. In future updates, you'll likely have issues (we say this from experience because people tried manually copying files in the past then created a stream of bugs against us when VS behavior changed).
The root issue is that MSBuild 15 introduced a breaking change in the handling of
<Import Project="$(WixTargetsPath)" Condition=" '$(WixTargetsPath)' != '' " /> <Import Project="$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets" Condition=" '$(WixTargetsPath)' == '' AND Exists('$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets') " /> <Target Name="EnsureWixToolsetInstalled" Condition=" '$(WixTargetsImported)' != 'true' "> <Error Text="The WiX Toolset v3 build tools must be installed to build this project. To download the WiX Toolset, see http://wixtoolset.org/releases/" /> </Target>
As well as removing the
However, the import still relies on
Therefore, I cannot say I understand how the modifications to the .wixproj is supposed to fix the issue.
For additional support contact wix-users mailing list.
I didn't know msbuild implicitly looked in both locations, even though the property appears to be set to a single path.
I updated all the .wixproj files I had, and I can confirm it seems to fix the issue.
Sorry for creating this duplicate, then, and thanks a lot for helping out.