blocks|key|1031001|text|我想我和你有同样的问题。我没有保存整个错误消息，但我的错误消息是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031002|‘不能加载文件或程序集'Microsoft.Build.Framework，Version=15.1.0.0，Culture=neutral，PublicKeyToken=b03f5f7f11d50a3a’或其依赖项之一。系统找不到指定的文件。|blockquote|1031003|我正在使用VisualStudio2017，并试图在Update-Database之后执行Add-Migration。|offset|length|style|CODE|1031004|为了解决这个问题，我关闭了Visual并重新打开了，然后再次运行Update-Database。|BOLD|1031005|这可能解决你的问题，也可能无法解决，但我想我会张贴，以防万一会有帮助。|1031006|entityMap^0|0|0|Q|F|19|D|0|A|F|W|F|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|T|8|@$G|U|H|V|I|J]|$G|W|H|X|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@$G|Z|H|10|I|M]|$G|11|H|12|I|J]]|9|@]|A|$]]|$1|N|3|O|5|6|7|13|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|Q|$]]

I believe I had the same issue as you did. I didn't save the whole error message, but my error message was

<blockquote>
 'Could not load file or assembly 'Microsoft.Build.Framework,
 Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or
 one of its dependencies. The system cannot find the file specified.'
</blockquote>

I am using Visual Studio 2017 and was trying to do <code>Update-Database</code> after <code>Add-Migration</code>.

To resolve the issue I closed Visual Studio and re-opened it, then re-ran <code>Update-Database</code> again.

This may or may not resolve your issue, but I thought I'd post just in case it would help.

blocks|key|1031519|text|这个问题的根本原因来自于devenv.exe.config文件到Microsoft.Build.Framework.dll的相对路径(请参阅Microsoft.Build.Framework.dll标记)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1031520|一些Visual扩展正在更改当前目录并使相对路径无效。|1031521|要修复它，请在C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Enterprise\Common7\IDE\目录中打开这个文件。并将所有..\..\MSBuild\15.0\Bin\替换为C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Enterprise\MSBuild\15.0\Bin\。|1031522|entityMap^0|C|H|W|T|1Y|T|0|0|7|23|2O|N|3E|28|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|K|$]]

The root cause of this problem comes from relative paths in the <code>devenv.exe.config</code> file to <code>Microsoft.Build.Framework.dll</code> (see xml tags).

Some Visual Studio Extensions are changing the current directory and makes relative paths invalid.

To fix it, open this file in the <code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\</code> directory. and replace all <code>..\..\MSBuild\15.0\Bin\</code> by <code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\</code>.

blocks|key|2538660|text|我们有过这个问题，下面是我们需要做的事情：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2538661|问题是，我们配置了一个名为HttpRuntime.Cache["somekey"的数据库命令拦截器HttpRuntime.Cache["somekey"]，由于某种原因，迁移命令无法运行。删除这种依赖后，所有命令都运行完美。也许HttpRuntime找不到Build？|offset|length|style|CODE|2538662|因此，当迁移命令无法查看是否存在类似问题时，请检查整个调用堆栈。|BOLD|2538663|entityMap^0|0|D|R|1D|R|36|B|0|R|4|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@$D|O|E|P|F|G]|$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@$D|V|E|W|F|J]]|9|@]|A|$]]|$1|K|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|L|$]]

We had this issue, and here is what we needed to do in our case:

Problem was that we had a database command interceptor <code>(IDbCommandInterceptor)</code> configured that called <code>HttpRuntime.Cache["somekey"</code>], and for some reason migration commands failed to run because of this. After removing this depencency, all commands ran perfect. Maybe <code>HttpRuntime</code> weren't able to find the Build Framework dll?

So check the entire callstack when migration commands fails to see if you have a similar problem.

blocks|key|823925|text|我找到了一个解决问题的方法，至少在运行VS+2017+Professional+15.5.2和实体框架6.1.1的环境中是这样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|823926|基本上，将DLL+(和一些相关的DLL)安装到GAC+()中，这个问题就会消失。|823927|遵循以下步骤：|823928|关闭Visual+2017的所有运行实例|ordered-list-item|823929|启动VisualStudio2017开发人员命令提示|823930|键入以下命令(将Professional替换为您的版本，企业或社区，或相应地调整路径)：|823931|gacutil+/i+"C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Framework.dll"

gacutil+/i+"C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.dll"

gacutil+/i+"C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Engine.dll"

gacutil+/i+"C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Conversion.Core.dll"

gacutil+/i+"C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Tasks.Core.dll"

gacutil+/i+"C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Utilities.Core.dll"|code-block|syntax|javascript|823932|重新启动Visual+2017|823933|本质上，当.NET试图加载DLL时，GAC+(在大多数情况下)将获得优先权，FileNotFoundException将消失，因为您的DLL现在将通过GAC解决。|823934|再说一遍，它对我很管用，它只是一个解决方法，它本身并不能解决核心问题，但至少当我尝试使用EF迁移时，我不必一直重新启动VS，这对我来说已经足够好了。|823935|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|15|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|H|7|16|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|17|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|18|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|Y|$]]

I've found a workaround that seems to resolve the issue for good, at least on my environment running VS 2017 Professional 15.5.2 and Entity Framework 6.1.1.

Basically, install the DLL (with a few related ones) into the GAC (Global Assembly Cache) and the issue will go away.

Follow these steps:

<ol>
<li>Close all running instances of Visual Studio 2017</li>
<li>Launch the Visual Studio 2017 Developer Command Prompt</li>
<li>Type the following commands (replace Professional with your edition, either Enterprise or Community, or adjust the path accordingly):</li>
</ol>

<pre><code>gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Framework.dll"

gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.dll"

gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Engine.dll"

gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Conversion.Core.dll"

gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Tasks.Core.dll"

gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Build.Utilities.Core.dll"
</code></pre>

<ol start="4">
<li>Restart Visual Studio 2017</li>
</ol>

In essence, the GAC will (in most cases) be given priority when .NET is trying to load a DLL and the FileNotFoundException will go away as your DLL will now be resolved through the GAC.

Again, it works for me and it's simply a workaround, it won't solve the core issue itself but at least I don't have to restart VS all the time when trying to work with EF migrations, and that's good enough for me.

blocks|key|823980|text|如果重新启动Visual不起作用，请转到任务管理器/流程资源管理器和技能VBCSCompiler.exe|type|unstyled|depth|inlineStyleRanges|entityRanges|data|823981|​|823982|📷|atomic|offset|length|823983|823984|建议使用过程资源管理器|823985|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/53bf38b30e68be6994aad74a6e363c0e.png|imageAlt|1|LINK|MUTABLE|url|https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer^0|0|0|0|1|0|0|0|4|7|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@$G|12|H|13|1|14]]|A|$]]|$1|I|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@$G|17|H|18|1|19]]|A|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]|U|$5|V|P|W|A|$X|Y]]]]

Just in case restarting Visual Studio does not work Go to Task Manager/ Process Explorer and skill VBCSCompiler.exe

<a href="https://i.stack.imgur.com/Mk51E.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Mk51E.png" alt="enter image description here"></a>

Suggest using <a href="https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer" rel="nofollow noreferrer">Process Explorer</a>

blocks|key|1031619|text|我丢失的文件或程序集版本与问题不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031620|当我试图发布我的ASP.net项目时，出现了这个错误|1031621|Microsoft.Build.Framework,+Version=4.0.0.0,+Culture=neutral,+PublicKeyToken=b03f5f7f11d50a3a|code-block|syntax|javascript|1031622|我通过安装Microsoft+Build+Tools+2015解决了这个问题|offset|length|1031623|我认为我的问题是因为我发布了一个项目，这个项目是用VS+2015在2017年建成的。希望能帮助有同样问题的人。|1031624|entityMap|0|LINK|mutability|MUTABLE|url|https://www.microsoft.com/en-us/download/details.aspx?id=48159^0|0|0|0|5|Q|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@$K|10|L|11|1|12]]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

My missing file or assembly version is different with the question.

I have this error when I tried to publish my ASP.net project

<pre><code>Microsoft.Build.Framework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
</code></pre>

I solved the problem by installing <a href="https://www.microsoft.com/en-us/download/details.aspx?id=48159" rel="noreferrer">Microsoft Build Tools 2015</a>

I think my problem caused by I publish project that was built with VS 2015 in VS 2017. Hope can help others that have same problem.

blocks|key|824034|text|关闭和重新打开+Visual就像一种魅力！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|824035|entityMap^0|0|2|3|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Closing and re-opening Visual Studio works like a charm!

blocks|key|2538929|text|感谢那些已经发帖的人。我的处境是通过以上的结合解决的。我已经有了几个版本的Visual+:+2015,2017,2019。在某个时候，MSBUILD的版本从15.1到15.9，我通过将C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\Professional\Common7\IDE\devenv.exe.config文件更新为指向15.9库来解决这个问题。下面是其中一个条目的示例：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2538930|<dependentAssembly>
++++++<assemblyIdentity+name="Microsoft.Build.Utilities.Core"+publicKeyToken="b03f5f7f11d50a3a"+culture="neutral"/>
++++++<bindingRedirect+oldVersion="2.0.0.0-99.0.0.0"+newVersion="15.9.0.0"/>
++++++<codeBase+version="15.9.0.0"+href="..\..\MSBuild\15.0\Bin\Microsoft.Build.Utilities.Core.dll"+/>
</dependentAssembly>|code-block|syntax|javascript|2538931|entityMap^0|2K|2M|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Thanks to those who already posted. My situation was solved by a combination of the above. I have had several version of Visual Studio: 2015, 2017, 2019. At some point the version of MSBUILD went from 15.1 to 15.9, and I solved this issue by updating the <code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe.config</code> file to point to the 15.9 library. Here is an example of one of the entries:
<pre><code>&lt;dependentAssembly&gt;
 &lt;assemblyIdentity name=&quot;Microsoft.Build.Utilities.Core&quot; publicKeyToken=&quot;b03f5f7f11d50a3a&quot; culture=&quot;neutral&quot;/&gt;
 &lt;bindingRedirect oldVersion=&quot;2.0.0.0-99.0.0.0&quot; newVersion=&quot;15.9.0.0&quot;/&gt;
 &lt;codeBase version=&quot;15.9.0.0&quot; href=&quot;..\..\MSBuild\15.0\Bin\Microsoft.Build.Utilities.Core.dll&quot; /&gt;
&lt;/dependentAssembly&gt;
</code></pre>

blocks|key|824135|text|在macOS上更新XCode/Mono组件时，我也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|824136|解决方案是将更新为最新版本。|824137|我认为这个问题是在使用新的MSBuild+Core3.0软件包中使用新的.NET工具的原因，该软件包安装了新的XCode/Mono版本。|824138|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I've faced with same issue when updated XCode/Mono components on macOS.

Solution is to update Visual Studio for Mac to latest version.

I think that issue cause in using new MSBuild tools from .NET Core 3.0 package which installed with new XCode/Mono version.

blocks|key|2538995|text|在我的例子中，一些东西(可能是NuGet)确实在web.config-File中添加了一个AssemblyBinding：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2538996|<dependentAssembly>
++++<assemblyIdentity+name="Microsoft.Build.Framework"+publicKeyToken="b03f5f7f11d50a3a"+culture="neutral"+/>
++++<bindingRedirect+oldVersion="0.0.0.0-15.1.0.0"+newVersion="15.1.0.0"+/>
</dependentAssembly>|code-block|syntax|javascript|2538997|删除依赖程序条目后，我可以再次发布该项目。|2538998|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case, something (maybe a NuGet-Update) did add an AssemblyBinding into the web.config-File:

<pre><code>&lt;dependentAssembly&gt;
 &lt;assemblyIdentity name="Microsoft.Build.Framework" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /&gt;
 &lt;bindingRedirect oldVersion="0.0.0.0-15.1.0.0" newVersion="15.1.0.0" /&gt;
&lt;/dependentAssembly&gt;
</code></pre>

After removing that dependentAssemby-Entry, I could Publish the Project again.

blocks|key|824203|text|我们的本地构建脚本使用较早版本的nuget.exe+(4.7.1.5393)来恢复NuGet包。更新到VisualStudio2019版本16.5.0后，我们开始收到此错误。更新到最新版本的nuget.exe+(5.4.0.6315)为我们解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|824204|nuget.exe可以在这里下载：https://www.nuget.org/downloads。|824205|entityMap|0|LINK|mutability|MUTABLE|url|https://www.nuget.org/downloads^0|G|9|R|A|1X|6|2N|9|2Y|A|0|0|9|H|V|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|H|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Our local build script was using an older version of <code>nuget.exe</code> (<code>4.7.1.5393</code>) to restore NuGet packages. We started getting this error after updating to Visual Studio 2019 version <code>16.5.0</code>. Updating to the latest version of <code>nuget.exe</code> (<code>5.4.0.6315</code>) fixed the issue for us.

<code>nuget.exe</code> can be downloaded here: <a href="https://www.nuget.org/downloads" rel="noreferrer">https://www.nuget.org/downloads</a>.

blocks|key|1031742|text|从2020年开始，这对我来说似乎是一个不受支持的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031743|在Azure+Build+Pipeline+>+NuGet+tool+installer步骤中，将Version+of+NuGet.exe+to+install更改为较新的版本，如5.4.0。检查https://dist.nuget.org/tools.json的版本。|offset|length|style|CODE|1031744|问题消失了，现在构建成功了。|1031745|entityMap|0|LINK|mutability|MUTABLE|url|https://dist.nuget.org/tools.json^0|0|1|K|O|K|1D|V|2I|5|2Q|X|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]|$D|V|E|W|F|G]|$D|X|E|Y|F|G]|$D|Z|E|10|F|G]]|9|@$D|11|E|12|1|13]]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

This worked for me - appears to be a non-support issue beginning in 2020.

In the <code>Azure Build Pipeline</code> > <code>NuGet tool installer</code> step, change <code>Version of NuGet.exe to install</code> to a newer version, like <code>5.4.0</code>. Check versions at <a href="https://dist.nuget.org/tools.json" rel="noreferrer">https://dist.nuget.org/tools.json</a>.

Issue disappeared and now builds successfully.

blocks|key|1031240|text|这对我是有效的:当我执行nuget还原命令时会发生错误。Nuget版本4.6.2。我有两种方法来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031241|使用Nuget+4.8.2及更高版本。gacutil+/i+"C:\Program+(x86)\Microsoft+Visual+/i|1031242|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This worked for me:
The error occurs when I execute the nuget restore command. Nuget version 4.6.2. I have two ways to solve this problem.

Use Nuget 4.8.2 and higher.
gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Build.Framework.dll

blocks|key|824418|text|在尝试了上述所有方法和运行更多的WCF应用程序之后，我仍然失败了。错误：Could+not+load+file+or+assembly+'Microsoft.Build.Framework,+Version=15.1.0.0..。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|824419|注意:尝试重新启动VS，PC，删除进程，清理VS缓存，nuget缓存，obj，bin，.vs，包文件夹|blockquote|824420|对我有效的是删除项目的*.csproj.user文件。显然它有一些过时的配置。花了4个小时想办法弄清楚。|824421|entityMap^0|G|3|10|24|0|0|B|D|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|L|$]]

After trying all of the above methods and more - running <code>WCF</code> app still failed for me. Error: <code>Could not load file or assembly 'Microsoft.Build.Framework, Version=15.1.0.0</code>..
<blockquote>
note: tried Restarting VS, PC, killing processes, cleaning up the VS caches, nuget caches, obj, bin, .vs, packages folders
</blockquote>
What worked for me is removing the projects' <code>*.csproj.user</code> file.. Apparently it had some obsolete configuration in it. Lost 4 hours trying to figure it out..

blocks|key|2539193|text|我重新启动了一次，然后我发现我一直在运行的本地web服务被另一个访问该端口的进程阻塞了。我检查了进程的运行情况，并使用TCPView终止了进程，所有这些似乎都重新开始工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2539194|entityMap|0|LINK|mutability|MUTABLE|url|http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx^0|1N|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I did a restart, following which I found that the local web service I have been running was blocked by another process which had taken that port. I checked the process running and and killed the process using <a href="http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx" rel="nofollow noreferrer">TCPView</a> and all seemed to start working again.

blocks|key|1031803|text|我在我的web.config中有这个部分，简单地删除它，然后它就开始工作了:)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1031804|<compilation+debug="true"+targetFramework="4.5.2">
++++<assemblies>
++++++++<add+assembly="Microsoft.Build.Framework,+Version=14.0.0.0,+Culture=neutral,+PublicKeyToken=B03F5F7F11D50A3A"/>
++++</assemblies>
</compilation>|code-block|syntax|javascript|1031805|entityMap^0|4|A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I had this part in my <code>web.config</code> and simply removed it and then it start working :)
<pre><code>&lt;compilation debug=&quot;true&quot; targetFramework=&quot;4.5.2&quot;&gt;
 &lt;assemblies&gt;
 &lt;add assembly=&quot;Microsoft.Build.Framework, Version=14.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A&quot;/&gt;
 &lt;/assemblies&gt;
&lt;/compilation&gt;
</code></pre>

blocks|key|824509|text|在我访问DLL之前调用"MSBuildLocator.RegisterDefaults();“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|824510|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Calling &quot;MSBuildLocator.RegisterDefaults();&quot; before DLLs are accessed worked for me.

blocks|key|2539331|text|问题:无法加载文件或程序集‘Microsoft.Build.Framework.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2539332|解决方案:我在我的项目中引用了Microsoft.Build.Framework+Nuget包，并将NuGet包的复制本地的引用设置为True，问题已经解决。|offset|length|style|BOLD|2539333|entityMap^0|0|F|P|1L|4|1V|4|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|I|$]]

Problem: Could not load file or assembly 'Microsoft.Build.Framework...
Solution: I had Microsoft.Build.Framework Nuget package referenced in my project and setting the reference for this NuGet package's Copy Local to True, issue was resolved for me.

blocks|key|824660|text|在我的Roslyn项目中，引用NuGet包Microsoft.Build.Locator并在创建MSBuildWorkspace之前调用MSBuildLocator.RegisterDefaults();解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|824661|entityMap^0|L|N|1C|G|1W|Y|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

In my Roslyn project, referencing the NuGet Package <code>Microsoft.Build.Locator</code> and calling <code>MSBuildLocator.RegisterDefaults();</code> before creating the <code>MSBuildWorkspace</code> solved this problem.

blocks|key|824672|text|我不得不安装带有.NET跨平台开发选项的visual。我也得到了通用的windows平台开发。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|824673|https://learn.microsoft.com/en-us/visualstudio/install/install-visual-studio?view=vs-2022|offset|length|824674|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2H|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

I had to install visual studio with the .NET cross-platform development option.
I did also get universal windows platform development too
<a href="https://learn.microsoft.com/en-us/visualstudio/install/install-visual-studio?view=vs-2022" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/visualstudio/install/install-visual-studio?view=vs-2022</a>

blocks|key|1031864|text|在使用macOS+6的.NET上，从6.0.1升级到6.0.2后，我开始看到这个错误。修复方法是卸载和重新安装dotnet-ef：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031865|dotnet+tool+uninstall+--global+dotnet-ef
dotnet+tool+install+--global+dotnet-ef|code-block|syntax|javascript|1031866|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

On macOS with .NET 6, I started seeing this error after upgrading form 6.0.1 to 6.0.2. The fix is to uninstall and reinstall dotnet-ef cli:
<pre class="lang-sh prettyprint-override"><code>dotnet tool uninstall --global dotnet-ef
dotnet tool install --global dotnet-ef
</code></pre>

blocks|key|1031408|text|OP没有将任何堆栈跟踪作为异常的一部分，但在我的示例中，调用堆栈中有对我版本的DbContext类的引用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1031409|在构造函数中，我检查环境，看看我们是否运行在Live上。这是因为如果迁移不是最新的，我不想抛出异常。|1031410|但是，为了进行此检查，它查找web.config的一个自定义部分。并且，在运行时，此代码创建此自定义部分的“实例”，以便在代码的各个区域中引用环境。|1031411|我不知道这是web.config的自定义部分，还是在我的代码中创建静态“实例”的方式，但这似乎是我异常的根源。|1031412|用#if+!DEBUG语句包装它可以确保PackageManager不会触发这段代码(反正这是不必要的)，而且我不再得到异常。|1031413|​|1031414|📷|atomic|1031415|1031416|我的建议是去掉你的DbContext。如果您使用的是自定义构造函数，请清空它并测试它是否有效。|1031417|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/b67bd32147096fa710d1019f11c8457c.png|imageAlt^0|13|9|0|M|4|0|E|A|0|0|1|A|0|0|0|1|0|0|0|9|9|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1D|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1H|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|S|3|O|5|6|7|1M|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12|13|-4]]]]

The OP doesn't include any of the stack trace as part of the exception, but in my case there was a reference in the call stack to my version of the <code>DbContext</code> class.
In the constructor I check the environment to see if we're running on <code>Live</code>. This is because I don't want to throw exceptions if the migrations aren't up to date.
However, in order to do this check it looks up a custom section of the <code>web.config</code>. And, during run time this code creates an &quot;instance&quot; of this custom section, so that the environment can be referred to in various areas of the code.
I don't know whether it's the custom section of the web.config or the way the static &quot;instance&quot; is created in my code, but it seems that this is the root of my exception.
Wrapping it in a <code>#if !DEBUG</code> statement ensures that the PackageManager doesn't trigger this code (which is unnecessary anyway) and I no longer get the exception.
<a href="https://i.stack.imgur.com/Xczgs.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Xczgs.png" alt="enter image description here" /></a>
My recommendation would be to strip back your <code>DbContext</code>. If you are using a custom constructor, empty it and test whether it works.

blocks|key|1031441|text|我也经历过用.Net+6进行开发的相同问题，但通过从NuGet+Packages+Management+安装解决了这个问题|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1031442|​|1031443|📷|atomic|1031444|1031445|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/0631fadc7b02cb0e0c617ee6b056239f.png|imageAlt^0|6|6|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|K|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

I've experienced the same issue developing with .Net 6 but I've fixed it by installing from NuGet Packages Management Microsoft.Build.Framework.
<a href="https://i.stack.imgur.com/kHRj3.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/kHRj3.png" alt="enter image description here" /></a>

When I try running the command "update-database", I get this exception:

<blockquote>
 Specify the '-Verbose' flag to view the SQL statements being applied
 to the target database. System.IO.FileNotFoundException: Could not
 load file or assembly 'Microsoft.Build.Framework, Version=15.1.0.0,
 Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its
 dependencies. The system cannot find the file specified. File name:
 'Microsoft.Build.Framework, Version=15.1.0.0, Culture=neutral,
 PublicKeyToken=b03f5f7f11d50a3a' 
 
 WRN: Assembly binding logging is turned OFF. To enable assembly bind
 failure logging, set the registry value
 [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There
 is some performance penalty associated with assembly bind failure
 logging. To turn this feature off, remove the registry value
 [HKLM\Software\Microsoft\Fusion!EnableLog].
 
 Could not load file or assembly 'Microsoft.Build.Framework,
 Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or
 one of its dependencies. The system cannot find the file specified.`
</blockquote>

Could not load file or assembly 'Microsoft.Build.Framework'(VS 2017)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

当我尝试运行命令"update-database“时，会得到以下异常：指定“详细”标志，以查看应用于目标数据库的SQL语句。System.IO.FileNotFoundException:无法加载文件或程序集“Microsoft.Build.Framework、Version=15.1.0.0、Culture=neut...

问无法加载文件或程序集“Microsoft.Build.Framework”(VS 2017)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法加载文件或程序集“Microsoft.Build.Framework”(VS 2017)EN