MS-Build 2017“ Microsoft. WebApplication.target”缺失

我正在尝试将我们的 buildserver (Jenkins)从 VisualStudio2015升级到2017。我们正在通过 MS-Build 进行建设。我已经下载并安装了本 回答中描述的 MS-Build 工具。如果我编译我的项目，我得到一个错误，Microsoft.WebApplication.targets没有找到。

详细错误:

 error MSB4226: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Microsoft\VisualStudio\v15.0\WebApplications\Microsoft.WebApplication.targets"

我在 MS-Build 目录中执行了一个查找:

PS C:\Program Files (x86)\MSBuild> dir -Recurse -Filter "Microsoft.WebApplication.targets"




Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications




Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       11.01.2012     00:23          19654 Microsoft.WebApplication.targets




Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications




Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       22.07.2013     01:25          19995 Microsoft.WebApplication.targets




Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications




Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       06.07.2015     21:55          20118 Microsoft.WebApplication.targets




Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\WebApplications




Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       22.07.2013     01:25          19995 Microsoft.WebApplication.targets

可以看到，这个文件存在于旧的编译器版本中，但是在 v15.0中没有。

我还在构建服务器上安装了 VisualStudio2017。如果使用 VisualStudio2017编译，项目将成功生成。

有没有解决这个问题的方法？一种可能的解决方案是生成一个从 C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\WebApplications点到旧版本14.0文件(位于 C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications下)的符号链接。

谢谢

110756 次浏览
小开
最佳答案

Looks like you are missing the workload for "Web development build tools": Microsoft.VisualStudio.Workload.WebBuildTools.

You can install it by downloading the build tools installer from here (VS2017) or here (VS2019) then running

vs_buildtools.exe --add Microsoft.VisualStudio.Workload.WebBuildTools

or opening vs_buildtools.exe and selecting the "Web development build tools" component in the GUI:

screenshot from GUI

小开

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.

  1. vs_buildtools.exe does not technically exist. I had to create a question asking where that file was. It was not obvious that vs_buildtools.exe is vs_buildtools_*******.exe and is the actual installation program. Additionally the the "-add ***" mentioned above is just a shorthand. One can go to the GUI and check both workflow tasks. That does the same thing. I wound up having the vs_buildtools file, though not needing it.

  2. VSB Pro still did not build my project. I got thrown the same error above. The secret sauce was simply to copy the WebApplicationsfolder in C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Microsoft\VisualStudio\v15.0 to C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0. I then rebuilt the project and all was fine. I placed the WebApplication.targets file at the expected location.

Why Microsoft could not have done that is beyond me. Also, why the separate installation. VS17 installs an enormous amount of stuff. Build Tools is implied, like always. Whatever.

I am posting this answer as hopefully it will help others. I fell into the trap and lost quite a bit of time with my project not building. I hope that this answer clarifies things a bit.

小开

how to create VS 2017 pro, asp.net MVC application and build it with Jenkins?

use vs 2017 pro in both dev machine and build server

Check that VisualStudio is set to 15
Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v15.0\WebApplications\Microsoft.WebApplication.targets" Condition="false"

set the msbuild tool
to C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\MSBuild.exe in jenkins global configuration manager

With jenkins, execute windows command batch:
retore nugets: "C:\Program Files (x86)\Jenkins\tools\nuget\NuGet.exe" restore "C:\Program Files (x86)\Jenkins\workspace\theapp_build\theapp.sln"

With jenkins, execute windows command batch:
MSBuild Build File: theapp.sln
Command Line Arguments: /nologo /t:restore /t:rebuild /p:Configuration="Debug" /p:VisualStudioVersion=15.0

小开

It is easy to install the 2017 build tools, with the WebBuildTools option already included, using chocolatey. Once you have installed it, type the following in an admin command prompt:

choco install visualstudio2017buildtools -y

For VS 2019, it's similar:

choco install visualstudio2019buildtools -y
小开

Copy WebApplications folder from

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0

to

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0

Or in your build script add the following line before compiling

Copy-Item "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications" "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\WebApplications" -Recurse -Force

Be sure to run it with elevated permissions

小开

I had a similar issue after having upgraded from Visual Studio 2015 to 2017. When I try to load the web application project, it throwed me the error message:

The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications\Microsoft.WebApplication.targets" was not found. Also, tried to find "WebApplications\Microsoft.WebApplication.targets" in the fallback search path(s) for $(VSToolsPath) - "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0" . These search paths are defined in "C:\Users\xxx\AppData\Local\Microsoft\VisualStudio\15.0_558e146f\devenv.exe.config". Confirm that the path in the declaration is correct, and that the file exists on disk in one of the search paths.

The solution to this error I found here.

In my case, the .csproj file contained the following lines:

<PropertyGroup>
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">14.0</VisualStudioVersion>
<VSToolsPath Condition="'$(VSToolsPath)' == ''">$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v14.0</VSToolsPath>
</PropertyGroup>

After replacing the v14.0 by v$(VisualStudioVersion) in the VSToolPath tag, the project could be loaded.

I also replaced the v14.0 by v10.0 in the VisualStudioVersion tag, as the solution in the above link shows. But for me it also worked by leaving it at 14.0.

Here is how these lines should look in the end:

<PropertyGroup>
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">10.0</VisualStudioVersion>
<VSToolsPath Condition="'$(VSToolsPath)' == ''">$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)</VSToolsPath>
</PropertyGroup>

If you don't have these lines at all in your .csproj, then you have to add them manually right BEFORE this line:

<Import Project="$(VSToolsPath)\Web\Microsoft.Web.Publishing.targets" Condition="'$(VSToolsPath)' != ''" />

In my case (slightly different error message but same problem) it was this line:

<Import Project="$(VSToolsPath)\WebApplications\Microsoft.WebApplication.targets" Condition="'$(VSToolsPath)' != ''" />

It seems that projects created with Visual Studio versions since 2011 contain the lines with the VSToolsPath redefinition, while older files did not. Visual Studio never added them automatically when upgrading to a newer VS version, which is why you should add them if they are not there.

Source of this information: https://developercommunity.visualstudio.com/content/problem/27735/project-fails-to-load-with-error-regarding-microso.html?childToView=123664#comment-123664 (click on Show more comments to see the full discussion thread - unfortunately I cannot directly link to comments in this "more" section.)

小开

I just use Visual Studio Installer to update Visual Studio Community 2017, then the problem is solved.

小开

For VS 2019, I fixed this by copying:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0

to

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio

小开

There can be multiple issues that cause this error, but it is generally due to missing files (example of my error below).

Invalid project `C:\xxxxx\Web.Mvc.csproj`. The imported project "C:\Program Files\dotnet\sdk\5.0.403\Microsoft\VisualStudio\v16.0\WebApplications\Microsoft.WebApplication.targets" was not found. Confirm that the expression in the Import declaration "C:\Program Files\dotnet\sdk\5.0.403\Microsoft\VisualStudio\v16.0\WebApplications\Microsoft.WebApplication.targets" is correct, and that the file exists on disk.

For myself, I am building a .NET 4.8 solution via powershell using the dotnet command, running against VS2019. The failing projects where created in VS2010/15/17.

As such to address the missing files, I simply created a symlink between the files it was looking for and the location it expected.

mklink /J "C:\Program Files\dotnet\sdk\5.0.403\Microsoft\VisualStudio" "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VisualStudio"

This resolved the issue and now I can build solutions programmatically (this should also work for other instances, providing you use the correct file paths to make the symlink).


提交答案