试图在构建服务器上构建我的项目给我以下错误:
Microsoft (R) Build Engine Version 4.0.30319.1
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\TeamData\Microsoft.Data.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
几个月前，我通过在Build Server上安装Visual Studio 2010解决了这个问题。但是现在我从头开始安装一个新的服务器，我想知道是否有更好的解决方案来解决这个问题。
我在CI/CD管道上构建SQL Server项目时遇到了这个问题。事实上，我在当地也遇到过，但我没有设法解决它。
对我有效的是使用MSBuild SDK，它能够从一组SQL脚本生成SQL Server Data-Tier Application包(.dacpac)，这意味着创建一个新项目。但是我想保留SQL Server项目，这样我就可以通过Visual Studio上的SQL Server对象资源管理器将它链接到活动数据库。我采取了以下步骤让它运行起来:
Kept my SQL Server project with the .sql database scripts.
Created a .NET Standard 2.0 class library project, making sure that the target framework was .NET Standard 2.0, as per the guidelines in the above link.
Set the contents of the .csproj as follows:
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="MSBuild.Sdk.SqlProj/1.0.0">
<PropertyGroup>
<SqlServerVersion>Sql140</SqlServerVersion>
<TargetFramework>netstandard2.0</TargetFramework>
</PropertyGroup>
</Project>
I have chosen Sql140 as the SQL Server version because I am using SQL Server 2019. Check this answer to find out the mapping to the version you are using.
Ignore the SQL Server project on build, so that it stops breaking locally (it does build on Visual Studio, but it fails on VS Code).
Now we just have to make sure the .sql files are inside the SDK project when it is built. I achieved that with a simple powershell routine on the CI/CD pipeline that would copy the files from the SQL Server project to the SDK project:
Copy-Item -Path "Path.To.The.Database.Project\dbo\Tables\*"
-Destination (New-item name "dbo\Tables" -Type Directory -Path "Path.To.The.DatabaseSDK.Project\")
PS: The files have to be physically in the SDK project, either in the root or on some folder, so links to the .sdk files in the SQL Server project won't work. In theory, it should be possible to copy these files with a pre-build condition, but for some obscure reason, this was not working for me. I tried also to have the .sql files on the SDK project and link them to the SQL Server project, but that would easily break the link with the SQL Server Object Explorer, so I decided to drop this as well.
解决方案是在构建服务器代理上安装可重新分发的包。它可以通过多种方式实现，下面将介绍其中3种方式。挑一个最适合你的。
使用UI安装程序
这是原来的答案
现在，在2017年，你可以用MSBuildTools安装WebApplication重定向。只需转到这个页面，下载MSBuild 2017工具，在安装时单击Web开发构建工具，即可安装这些目标:
这将导致默认情况下在C:\Program Files (x86)\Microsoft VisualStudio\ 2017\BuildTools\MSBuild\Microsoft\VisualStudio\v15.0\WebApplications中安装缺失的库
使用命令行
免责声明:我没有测试过以下任何建议
正如@PaulHicks和@WaiHaLee在评论中建议的那样，它也可以从CLI以无头模式(没有ui)安装，这实际上可能是解决移除服务器问题的更好方法。
解决方案A -使用包管理器(choco)
choco install visualstudio2017-workload-webbuildtools
解决方案B -运行安装程序在无头模式
请注意，这是在原始答案中建议使用的相同安装程序
vs_BuildTools.exe --add Microsoft.VisualStudio.Workload.WebBuildTools --passive
我的解决方案是这里几个答案的混合。
我检查了构建服务器，Windows7/NET4.0 SDK已经安装，所以我确实找到了路径:
C:\Program Files (x86)\MSBuild\Microsoft\ VisualStudio\v9.0\WebApplications\Microsoft.WebApplication.targets
但是，在这一行:
<进口项目=”(MSBuildExtensionsPath美元)\ Microsoft \ VisualStudio v9 WebApplication 0 WebApplications \ Microsoft。很明显" - >
$(MSBuildExtensionsPath)扩展到C:\Program Files\MSBuild，其中没有路径。
因此，我所做的就是创建一个符号链接，使用下面的命令:
mklink /J "C:\Program Files\MSBuild\Microsoft\VisualStudio" "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio"
通过这种方式，$(MSBuildExtensionsPath)扩展到一个有效的路径，应用程序本身不需要更改，只需要在构建服务器中更改(也许可以在每个构建中创建符号链接，以确保这一步不会丢失并被“记录”)。
