Net 4.7 is the latest framework version installed. The build server is running Build Tools 2017 on Windows 7 and. installer as well as the 3.14.0.712 weekly installer. The WiX toolset installer does not appear to look for this path at install, because even after installing on our build server, I had to manually copy files from C:\Program Files (x86)\MSBuild\Microsoft. However, when only the bare Build Tools are installed (eg on a build server), the path resoves to C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Microsoft. In this case, wix targets are correctly installed in this path. When installed on a machine with a full VS installation (eg the professional version), this path resolves to C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft. Combining these two paths leads to paths that don't exist, causing the project file to be invalid, causing the restore to fail. Referenced in the above issues, the wix targets are imported from "$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets" But since NuGet is picking MSBuild 16.0, variables like (MSBuildExtensionsPath32) are things like C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild. ![]() 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. Before marking this as duplicate, please note that I have seen issues #5622 and #5525.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |