I wound up having the vs_buildtools file, though not needing it. One can go to the GUI and check both workflow tasks. Additionally the the "-add ***" mentioned above is just a shorthand. It was not obvious that vs_buildtools.exe is vs_buildtools_*******.exe and is the actual installation program. I had to create a question asking where that file was. Vs_buildtools.exe does not technically exist.
The accepted answer above is technically correct just incomplete, a bit confusing, at least for me, and needed one extra step to get Visual Build Professional working. The project succeeds to build if I compile with Visual Studio 2017.Īny hints how to solve this problem? One possible solution is to generate a symbolic link from C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\WebApplications point to the old v14.0 files (located under C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications). I also have installed Visual Studio 2017 on the build-server. a- 21:55 20118 ĭirectory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\WebApplicationsĪs can be seen the file exists for old compiler versions, but for v15.0 it is missing. a- 01:25 19995 ĭirectory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications
a- 00:23 19654 ĭirectory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications PS C:\Program Files (x86)\MSBuild> dir -Recurse -Filter ""ĭirectory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications
0 kommentar(er)
