EntityDeploySplit错误

本文介绍了EntityDeploySplit错误 - Microsoft.Data.Entity.Build.Tasks.dll丢失的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

无法从程序集 C：\Program文件（x86）\MSBuild\12.0\bin\Microsoft.Data.Entity加载EntityDeploySplit任务。 Build.Tasks.dll。可以不加载文件或程序集'file：/// C：\Program Files （x86）\MSBuild\12.0\bin\Microsoft.Data.Entity.Build.Tasks。 dll或一个的依赖关系。该系统找不到指定的文件。 确认声明正确，程序集及其所有依赖项可用，并且该任务包含实现Microsoft.Build.Framework.ITask的公共类。

有没有办法单独安装？默认情况下，此程序集包含在哪里？

更新：在查找EntityClean任务时，这也将显示出来。我倾向于认为它首先检查这个bin，因为另一个正在运行它的开发人员尝试了一个干净的/重建，然后开始显示。

解决方案

我遇到这个问题，能够修复它，如下所述。您的路径和变量可能不同。

我发现，当我的项目构建它指向这个目标文件：

C：\程序文件（x86）\MSBuild\12.0\Bin\Microsoft.Data.Entity.targets

该目标文件似乎只是一个占位符。该文件中有一个Import元素，它指向运行位于该路径上的目标文件的 $（MSBuildFrameworkToolsPath）\Microsoft.Data.Entity.targets 。我搜索注册表，发现 MSBuildFrameworkToolsPath 是一个注册表项，值为 C：\Windows\Microsoft.NET\Framework\v4 .0.30319\

我去了引用的目标文件，并搜索 UsingTask 在我的异常中指定的元素。在 UsingTask 元素内， AssemblyFile 属性指向 $（MSBuildBinPath）\Microsoft .Data.Entity.Build.Tasks.dll 。我搜索注册表，发现MSBuildBinPath注册表项指向 c：\Windows\Microsoft.NET\Framework\v3.5\

我不知道为什么指出，也许框架或Visual Studio安装没有清理它。最后，我将所有我的 UsingTask 元素'$ code>的属性更改为：

$（MSBuildFrameworkToolsPath）\Microsoft.Data.Entity.Build.Tasks.dll

我使用了MSBuild Bin目标文件中的相同变量。

希望这有帮助。

After a clean Windows reformat and installing Visual Studio 2013, trying to build a project with database-first Entity Framework edmx files yields the following error:

The "EntityDeploySplit" task could not be loaded from the assembly C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Data.Entity.Build.Tasks.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Data.Entity.Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

Is there some way to install this separately? What is this assembly included with by default?

UPDATE: This also manifests itself when looking for the EntityClean task. I'm inclined to think that it checks the bin first, since another developer who was running it fine tried a clean / rebuild and then this started showing up.

解决方案

I ran into this problem and was able to fix it as I have described below. Your paths and variables may be different.

I found that when my project builds it points to this target file:

C:\Program Files (x86)\MSBuild\12.0\Bin\Microsoft.Data.Entity.targets

That target file appears to just be a placeholder. There is an Import element, in that file, that points to $(MSBuildFrameworkToolsPath)\Microsoft.Data.Entity.targets which runs the target file located at that path. I searched registry and found that MSBuildFrameworkToolsPath is a registry entry with the value of C:\Windows\Microsoft.NET\Framework\v4.0.30319\

I went to the targets file that was referenced and search for the UsingTask element that was specified in my exception. Inside the UsingTask element, the AssemblyFile attribute was pointed to $(MSBuildBinPath)\Microsoft.Data.Entity.Build.Tasks.dll. I searched the registry and found that the MSBuildBinPath registry entry was pointed to c:\Windows\Microsoft.NET\Framework\v3.5\

I'm not sure why it was pointed to that, maybe a Framework or Visual Studio installation didn't clean it up. Finally, I changed all my UsingTask elements' AssemblyFile attributes to:

$(MSBuildFrameworkToolsPath)\Microsoft.Data.Entity.Build.Tasks.dll

I used the same variable that was in the MSBuild Bin target file.

Hope this helps.