blocks|key|3324493|text|我似乎记得几个月前也有过类似的问题。我通过将引用的DLL复制到发布文件夹暂时解决了这个问题，从而满足了Visual+Studio的期望。后来，我在实际代码中发现了对Release+DLL的引用。您应该尝试在整个项目中搜索\release\project.dll。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3324494|此外，我还注意到，Visual+Studio单元测试项目有时会在指向目标DLL的每个测试方法上放置一个"DeploymentItem“属性，如果您在调试和发布之间切换，如果DLL不再位于预期位置，Visual+Studio可能会感到困惑。根据我的经验，如果您没有将这些属性作为“单一部署”场景的一部分放在那里，则可以安全地删除这些属性。|3324495|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|$]]

I seem to recall having a similar problem a few months ago. I solved it temporarily by copying the referenced DLL to the Release folder, thus satisfying Visual Studio's expectations. Later, I discovered the reference to the Release DLL in my actual code. You should try doing a search through the entire project for \release\project.dll. 

Also, I have noticed that Visual Studio unit test projects sometimes put a "DeploymentItem" attribute on each of the test methods pointing to your target DLL, and if you switch between Debug and Release, Visual Studio can get confused if the DLL is no longer in the expected location. In my experience, these attributes can be safely deleted if you didn't put them there yourself as part of a "single deployment" scenario.

blocks|key|339486|text|您检查配置管理器设置了吗？在项目设置对话框的右上角。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|339487|有时，在所有版本条目之间会出现一个调试条目。如果是这样，那么由解决方案的依赖关系图创建的自动依赖关系就会变得完全混乱。|339488|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|$]]

Did you check the Configuration manager settings? In the project settings dialog top right corner.

Sometimes it happens that between all the release entries a debug entry comes in.
If so, the auto dependency created by the dependency graph of the solution gets all confused.

blocks|key|3111530|text|当您说您删除了对这些项目的引用并重新添加它们时，您究竟是如何重新添加它们的？您是否在Visual+Studio中使用了“添加引用”对话框中的“浏览”选项卡？或者，您是否使用了“项目”选项卡(它列出了您的解决方案中的相邻项目)？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3111531|编辑：如果您使用“浏览”选项卡，并手动添加对位于/Release文件夹中的.dll的引用，则无论您当前处于什么模式(调试或发布)，Visual+Studio都将始终在该位置查找.dll。|offset|length|style|BOLD|3111532|如果您从Release文件夹中删除了实际的.dll文件(手动或通过执行“清理解决方案”)，那么您的引用将会中断，因为该.dll不存在。|3111533|我建议删除对ProjectX.dll的引用，然后重新添加它--但这一次，使用“添加引用”对话框中的“项目”选项卡。当您以这种方式添加引用时，Visual+Studio知道从何处获取适当的.dll。如果你处于调试模式，它将从/Debug文件夹中获取它。如果处于发布模式，则为/Release文件夹。您的构建错误应该会消失，而且在调试模式下，您也不再(不正确地)引用发布.dll。|3111534|entityMap^0|0|0|2|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

When you say you deleted references to those projects and re-added them, how did you re-add them, exactly? Did you use the "Browse" tab in the "Add Reference" dialog in Visual Studio? Or, did you use the "Projects" tab (which lists neighboring projects in your solution)?

Edit: If you use the "Browse" tab, and manually add the reference to your .dll that is located in the /Release folder, then Visual Studio will always look for the .dll in that location, regardless of what mode you're currently in (Debug or Release).

If you removed the actual .dll file from the Release folder (either manually or by doing "Clean Solution"), then your reference will break because the .dll does not exist.

I'd suggest removing the reference to ProjectX.dll, and add it in again--but this time, use the "Projects" tab in the "Add Reference" dialog. When you add a reference this way, Visual Studio knows where to get the appropriate .dll. If you're in Debug mode, it will get it from the /Debug folder. If in Release mode, the /Release folder. Your build error should go away, and you also will no longer be (improperly) referencing a Release .dll while in Debug mode.

blocks|key|3324579|text|我们经常遇到这个问题，但只有在引用C#项目中的C%2B%2B/CLI项目时才会遇到这个问题。这显然是微软决定不修复的Visual+Studio的一个深层次的错误，因为它“太复杂”，他们承诺对C%2B%2B构建系统进行全面检查，现在目标是在2010年的Visual+Studio中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3324580|那是一段时间以前的事了，也许这个修复在2008年甚至进入了Visual+Studio；我不再跟进它了。但是，我们的典型解决方法是|3324581|Visual+Studio+Switch+configuration|3324582|Restart+|unordered-list-item|3324583|3324584|Build+the+solution|3324585|3324586|3324587|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|S|8|@]|9|@]|A|$]]|$1|I|3|-4|5|H|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|H|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|O|$]]

We have that problem quite often, but only with references to C++/CLI projects from C# projects. It's obviously a bug deep down in Visual Studio that Microsoft decided not to fix, because it's 'too complex' and they promised an overhaul of the C++ build system which is now targeted for Visual&nbsp;Studio&nbsp;2010.

That was some time ago, and maybe the fix even went into Visual&nbsp;Studio&nbsp;2008; I didn't follow up on it any more. However, our typical workaround was

<ul>
<li>Switch configuration</li>
<li>Restart Visual Studio</li>
<li>Build the solution</li>
</ul>

blocks|key|3324604|text|我以前遇到过这个问题，我发现解决它的唯一方法是运行Clean+Solution，然后重新启动Visual+Studio。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3324605|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|$]]

I've had this problem before and the only way I've found to solve it is to run Clean Solution and then restart Visual Studio.

blocks|key|341954|text|此问题是由pdb文件或CodeContracts引起的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341955|要解决此问题，请执行以下操作：|341956|对于临时构建，请清除输出文件夹并重新生成solution.|341957|Re-Configure+|unordered-list-item|341958|+CodeContracts或将其禁用。|ordered-list-item|341959|341960|341961|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

This problem is due to pdb files or CodeContracts.

To resolve it:

<ol>
<li>Clean your output folder and rebuild the solution.</li>
<li>Re-Configure the CodeContracts or disable it for temporary build.</li>
</ol>

blocks|key|3111667|text|在我有多个项目的解决方案中(通常是netTiers项目，我已经更新了一个或多个针对4.0框架的子项目)，我也看到了这个错误。删除它可能会有问题。然而，通常可以通过首先修复子项目中的所有其他错误(例如，任何丢失的引用)，单独重新构建这些子项目，然后在Visual+Studio中移除/重新添加对这些子项目的任何引用，来解决这个问题。就我个人而言，我几乎没有机会通过单独清理解决方案来解决这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3111668|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|$]]

I've also seen this error in solutions where I have multiple projects (usually netTiers projects where I've updated one or more of the sub-projects to target the 4.0 framework). It can be problematic to remove. Oftentimes it can be resolved, however, by first fixing all other errors in sub-projects (eg, any missing references), individually rebuilding those sub-projects, then removing/adding back any references to those sub-projects in Visual Studio. Personally, I've had little luck resolving this error by cleaning the solution alone.

blocks|key|3111725|text|我遇到了这个问题，这是由于有问题的库(dll)中的一个无效方法没有返回值，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3111726|public+bool+DoSomething()
{
+++//I+never+bothered+putting+code+here....

}|code-block|syntax|javascript|3111727|当我对此进行注释时，所有内容都进行了编译:)|3111728|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|$]]

I had this problem and it was due to an invalid method in the offending library (dll) that did not return a value, e.g.

<pre><code>public bool DoSomething()
{
 //I never bothered putting code here....

}
</code></pre>

When I commmented this out everything compiled :)

blocks|key|339616|text|当你签出一个包含多个项目的解决方案，这些项目之间有引用，并且你以前没有构建过它时，似乎就会发生这种情况。如果您直接引用了‘ll，而不是引用项目，则会收到以下消息。应始终使用“添加引用”对话框中的“项目”选项卡向同一解决方案中的项目添加引用。这样，VS就可以知道构建解决方案的正确顺序|type|unstyled|depth|inlineStyleRanges|entityRanges|data|339617|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|$]]

It seems to happen when you checkout a solution with multiple projects that have references between them, and you haven't built it before. If you have references directly to the dlls, instead of referencing the project, you'll get this message.
You should always use the Projects tab in the Add Reference dialog to add a reference to a project in the same solution. This way, VS can know the correct order in which to build the solution

blocks|key|339633|text|我们最近在从Office+2007升级到Office+2010后遇到了这个问题--我们不得不手动将项目中的引用更改为我们在某些项目中使用的Office互操作版本14。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|339634|希望这能有所帮助--我们花了几天时间才弄清楚。|339635|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|$]]

We recently ran into this issue after upgrading to Office 2010 from Office 2007 - we had to manually change references in our project to version 14 of the Office Interops we use in some projects.

Hope that helps - took us a few days to figure it out.

blocks|key|3111843|text|正如Vidar所描述的那样，我今天也发生了同样的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3111844|我在Helper库(被其他项目引用)中有一个构建错误，编译器没有告诉我Helper库中有错误，而是列出了MetaFile-not-found类型错误的列表。更正Helper+Library中的构建错误后，MetaFile错误就消失了。|3111845|在VS中有什么设置可以改善这一点吗？|3111846|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|$]]

same happened to me today as described by Vidar. 

I have a Build error in a Helper Library (which is referenced by other projects) and instead of telling me that there's an error in Helper Library, the compiler comes up with list of MetaFile-not-found type errors. After correcting the Build error in Helper Library, the MetaFile errors gone.

Is there any setting in VS to improve this?

blocks|key|344573|text|有时，VS2010会将我的配置从任何CPU切换到混合平台。发生这种情况时，我会收到以下错误消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|344574|为了解决这个问题，我切换回任何CPU：|344575|在解决方案上单击|344576|右键，然后选择Configuration+Properties上的properties.|ordered-list-item|344577|Click，然后选择Configuration+|344578|...按钮。在Active+solution+platform下选择Any+|344579|344580|344581|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|V|8|@]|9|@]|A|$]]|$1|M|3|-4|5|H|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

Sometimes VS2010 switches my configuration from Any CPU to Mixed Platforms. When this happens I get this error message. 

To resolve it I switch back to Any CPU: 
1. Right click on the solution and select properties. 
2. Click on Configuration Properties and then the Configuration Manager... button. 
3. Under Active solution platform select Any CPU

blocks|key|339668|text|我也遇到了同样的问题。包含50%2B项目的大型visual+studio解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|339669|所有引用都是作为项目添加的。项目构建顺序是正确的(右键单击项目并选择构建顺序)。|339670|然而，当构建一些更高级别的项目时，他们所依赖的“根”项目并没有构建。|339671|问题是这些项目没有被选择在当前配置下构建(不知道这是如何发生的)。|339672|要检查这一点，请选择“配置管理器”(构建菜单)e检查有问题的项目是否设置为构建。|339673|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I had the exact same problem. Big visual studio solution with 50+ projects.

All references were added as projects. 
Project build order was correct (right click on project and select build order). 

However when building some of the higher level projects the "root" project they depended on were not built.

The problem was that these projects were not selected to build under the current configuration (don't know how this happened). 

To check this select "Configuration Manager" (Build menu) e check if the problematic projects are set to build.

blocks|key|3111971|text|我也有同样的问题。我注意到我的db上下文(EF4)位于项目dll中，由于某种原因无法识别。我删除了它，并创建了另一个。这就解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3111972|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|$]]

I had the same problem. I noticed that my db context (EF4) that was located in the project dll wasn't recognize for some reason. I deleted it and created another one instead. and that solved it for me.

blocks|key|3112018|text|今天也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3112019|我的应用程序，一个Windows窗体应用程序，意外地引用了它自己。真奇怪。|3112020|一旦删除，错误也就消失了。|3112021|每当我将位于Windows窗体项目本身中的用户控件拖动到窗体时，都会添加该引用。|3112022|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Had the same problem today.

My application, a Windows Forms applications, accidently had a reference to itself. Weird.

Once removed, the error went away.

The reference got added each time I dragged a user control, located in the Windows Forms project itself, to a form.

blocks|key|344644|text|我发现，当我仍然在接口中有一个类实现的方法声明，但后来我已经删除了它，并且忘记了从接口中删除它时，我通常会发生这种情况。我通常每30分钟保存一次整个解决方案，如果找不到错误，就恢复到以前的版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|344645|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|$]]

I find that this usually occurs to me when i still have a method declaration in an interface, which a class implements, but that i had later removed and had forgotten to remove it from the interface as well. I usually just save the entire solution every 30mins n then just revert back to an earlier version if i cant find the error.

blocks|key|3325063|text|Everyone+is+correct...try+everything...(按照浪费的时间顺序排列)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325064|3325065|你有错误的代码吗？先解决这个问题。|ordered-list-item|3325066|Clean+Solution+&+Restart+Visual+Studio|3325067|删除/添加带有较大项目的构建顺序，并将项目之间的dlls复制到关联的bin文件夹中|3325068|Go喝点咖啡，玩弹球，然后回来tomorrow...you可能会在这段时间想些别的事情。|3325069|3325070|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Everyone is correct...try everything...(in order of a little to a lot of time wasted)

<ol>
<li>Do you have bad code? Fix that first.</li>
<li>Clean Solution &amp; Restart Visual Studio</li>
<li>Remove / Add References</li>
<li>Check your build order w/ larger projects and verify</li>
<li>Manually rebuild sub-projects</li>
<li>Manually copy dlls between projects into associated bin folders</li>
<li>Go get some coffee, play some pinball and come back tomorrow...you may think of something else in the meanwhile.</li>
</ol>

blocks|key|344676|text|在我的案例中，它是由两件事引起的(VS.2012)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|344677|1)其中一个项目是为AnyCPU而不是x86配置的|344678|2)被引用的项目以某种方式取消选中了"Build“复选框。|344679|请务必检查您的Build+%7C+Configuration+Manager，以获得正在构建的内容以及针对哪个平台的概述。也要确保你检查了Debug和Release，因为它们可能有不同的设置。|344680|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

In my case it was caused by two things (VS.2012):

1) One of the projects was configured for AnyCPU instead of x86

2) A project that was referenced had somehow the "Build" checkbox unchecked.

Do check your Build | Configuration Manager to get an overview of what is being built and for which platform. Also make sure you check it for both Debug &amp; Release as they may have different settings.

blocks|key|342157|text|检查您的项目路径。它不应包含逗号和空格等不规则字符|type|unstyled|depth|inlineStyleRanges|entityRanges|data|342158|例如，这是不正确的路径:+d:\my+applications\Project1|342159|这就是真正的path+d:\my_applications\Project1|342160|当磁盘中的路径中存在非字母和数字字符时，visual+studio无法生成项目，并且不会显示此错误的消息！|342161|此外，一些安装工具在开始安装时也存在同样的问题，无法解压缩。|342162|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

CHECK YOUR PROJECT PATH. It should have no irregular character like comma and space

for example this is incorrect path:
d:\my applications\Project1

and this is true path
d:\my_applications\Project1

The visual studio cannot build the project when there is a non alphabetic and numeric character in its path in disk and it show no message for this fault!

Also some installation tools have same problem when they start installation and can not be extracted.

blocks|key|341100|text|我也有同样的问题。手动删除和添加dlls没有任何帮助。ClassLibraries没有编译所有项目，并且在项目的...\bin\Debug文件夹中丢失，因为我错误地清理了解决方案。，因为类库没有编译，这意味着在这些子项目中的某个地方可能有一些错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|341101|解决方案：由于我的dlls是针对...\bin\Release文件夹的，所以我尝试在发布模式下重新构建，但在其中一个子项目的一行上发现了错误。解决错误并重新构建解决方案消除了构建错误。|341102|entityMap^0|1K|D|2I|K|0|0|5|G|F|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

I had the same problem. Manually removing and adding the dlls did not help. ClassLibraries did not compile for all the projects and were missing in the ...\bin\Debug folder for the project [because I cleaned solution by mistake]. Since the class library did not compile that means there may be some errors somewhere in one of those sub projects.

Solution: Since my dlls were there for the ...\bin\Release folder, I tried to rebuild on Release mode and found an error on one line in one of the sub projects. Solving the error and rebuilding the solution got rid off the build error.

blocks|key|341111|text|对于我来说，Visual+Studio创建了一个类型为"Visual+Studio+Solution+User+Options“的projectname.v11。我删除了这个文件并重新启动，一切正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341112|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|$]]

For me Visual Studio had created a projectname.v11 of type "Visual Studio Solution User Options". I deleted this file and restarted and everything was fine.

blocks|key|3325239|text|我最终删除了我的引用(我已经使用projects选项卡正确地添加了它们，它们过去构建起来也很好)，手动编辑我的.csproj文件，删除不属于我的奇怪条目--并将调试和发布、x86和x64以及任何cpu的输出都设置为"\bin“--我构建了它一次，然后重新添加了引用(再次使用projects选项卡)，然后一切都开始对我起作用了。根本不需要重新启动Visual+Studio。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325240|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|$]]

I ended up deleting my references (I had added them properly using the projects tab, and they used to build just fine), hand editing my .csproj files and removing bizarre entries that didn't belong -- and setting my outputs for debug and release, x86 and x64 and any cpu to all be "\bin" -- I built it once, then re-added the reference (again, using the projects tab), and everything started working again for me. Didn't have to restart Visual Studio at all.

blocks|key|341124|text|我遇到了同样的问题，这个问题背后的原因是引用项目的dll文件正在被其他进程使用。在我的例子中，我正在调试一个应用程序，并且应用程序附加了visual+studio调试器。当我重新构建另一个使用同一项目的应用程序时，我得到了这个错误。在解除连接之后，我能够成功地构建第二个应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341125|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|$]]

I had the same issue and the reason behind this issue is that the dll file of reference project is being used by some other process. In my case, I was debugging an application and application was attached with visual studio debugger. When I was re-building another application which is using same project, then I was getting this error. After de-attaching, I was able to build second application successfully.

blocks|key|3325269|text|此问题已解决。我打开包管理器设置，点击“允许NuGet下载缺少的包”。现在可以构建项目了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325270|https://github.com/gitextensions/gitextensions/issues/1969|offset|length|3325271|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1M|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]]]]

This issue has been resolved. I opened up the Package Manager Settings and clicked "Allow NuGet to download missing packages". The project now builds.

<a href="https://github.com/gitextensions/gitextensions/issues/1969" rel="nofollow">https://github.com/gitextensions/gitextensions/issues/1969</a>

blocks|key|341135|text|在我的例子中，我的代码中有一些错误。Visual+Studio显示的是您的错误，而不是实际的错误，如语法错误或未知的类名。尝试清理解决方案并一个接一个地构建项目。这样，您就会发现实际的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341136|同样，这也是导致我出错的原因。|341137|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|$]]

In my case, I had some errors in my code. Visual Studio showed the error you had instead of the actual errors, like syntax errors or unknown class names. Try cleaning the solution and building project after project. This way you will discover the actual errors.

Again, this is just what cause the error for me.

blocks|key|3112353|text|对我来说，这是由于Build目标被重写为不输出dll造成的。删除此选项以回退到默认构建目标修复了此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3112354|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|$]]

For me this was caused by the Build target having been rewritten to not output the dll. Removing this to fall back on the default Build target fixed the issue.

blocks|key|339898|text|今天我也遇到了这个问题。我的问题是由循环依赖引起的。项目A引用项目B，反之亦然。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|339899|entityMap^0|I|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I also had this problem today. Mine was caused by a cyclic dependency. Project A referenced Project B and vice versa.

blocks|key|341185|text|您是否在项目中使用SQLMETAL这样的数据库代码生成工具？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341186|如果是这样的话，你可能会面临一个多元化到非多元化的过渡问题。|341187|在我的例子中，我注意到一些旧的复数(*)表名(默认情况下，SQLMETAL会在表名的末尾添加一个"s“字母)对SQLMETAL生成的类进行表引用。|offset|length|style|BOLD|341188|因为，我最近禁用了名称的复数，在重新生成一些与数据库相关的类之后，其中一些类丢失了它们的"s“前缀。因此，对受影响的表类的所有引用都无效。出于这个原因，我有几个编译错误，如下所示：|341189|341190|+'xxxx‘不包含'TableNames’的定义，并且找不到接受类型为'yyyy‘的第一个参数的扩展方法'TableNames’(是否缺少using指令或程序集引用？)|blockquote|341191|341192|341193|正如你所知道的，我只接受错误来防止程序集被编译。也就是说，缺少的程序集可链接到依赖程序集，从而导致原始的“元数据文件'XYZ‘找不到”|341194|在手动修复受影响的类表引用到它们的当前名称(无复数)后，我终于能够让我的项目恢复生机了！|341195|(*)如果启用了选项Visual+Studio+>+Tools+menu+>+Options+>数据库Tools+>+O/R+Designer+>名称复数<+code+>E217，某些SQLMETALl代码生成器会在某些生成的表类的末尾添加“E219”字母，尽管表在目标数据库上没有"s“后缀。欲了解更多信息，请访问http://msdn.microsoft.com/en-us/library/bb386987(v=vs.110).aspx。|341196|这篇文章有很多好的建议。又加了一个。|341197|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/bb386987%2528v=vs.110%2529.aspx^0|0|0|1D|1|0|C|2|19|1|0|0|0|0|0|0|0|Q|A|13|7|1C|8|1N|C|21|45|4E|1R|0|0|0|I|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|19|8|@$F|1A|G|1B|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1C|8|@$F|1D|G|1E|H|I]|$F|1F|G|1G|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1I|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1L|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1M|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1N|8|@$F|1O|G|1P|H|I]|$F|1Q|G|1R|H|I]|$F|1S|G|1T|H|I]|$F|1U|G|1V|H|I]|$F|1W|G|1X|H|I]]|9|@$F|1Y|G|1Z|1|20]]|A|$]]|$1|X|3|Y|5|6|7|21|8|@$F|22|G|23|H|I]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]]]

Are you using a database code generation tool like SQLMETAL in your project?

If so, you may be facing a pluralized to unpluralized transition issue.

In my case, I have noted that some old pluralized (*) table names (upon which SQLMETAL adds, by default, an "s" letter at the end) table references to classes generated by SQLMETAL.

Since, I have recently disabled Pluralization of names, after regerating some database related classes, some of them lost their "s" prefix. Therefore, all references to affected table classes became invalid. For this reason, I have several compilation errors like the following:

<blockquote>
 'xxxx' does not contain a definition for 'TableNames' and no extension method 'TableNames' accepting a first argument of type 'yyyy' could be found (are you missing a using directive or an assembly reference?)
</blockquote>

As you know, I takes only on error to prevent an assembly from compiling. And that is the missing assemply is linkable to dependent assemblies, causing the original "Metadata file 'XYZ' could not be found"

After fixing affected class tables references manually to their current names (unpluralized), I was finnaly able to get my project back to life!

(*) If option Visual Studio > Tools menu > Options > Database Tools > O/R Designer > Pluralization of names is enabled, some SQLMETALl code generator will add an "s" letter at the end of some generated table classes, although table has no "s" suffix on target database. For further information, please refer to <a href="http://msdn.microsoft.com/en-us/library/bb386987%28v=vs.110%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/bb386987(v=vs.110).aspx</a>

This post has lots of good advices. Just added one more.

blocks|key|3325359|text|在我的例子中，在合并过程中，解决方案文件似乎缺少一些项目引用。手动将项目重新添加到解决方案中修复了该问题。您也可以手动编辑解决方案文件，但您需要小心，并知道自己在做什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325360|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|$]]

In my case, during a merge, it seems the solution file was missing some project references. Manually re-adding the project to the solution fixed it. You can also manually edit the solution file but you need to be careful and know what you are doing.

blocks|key|341241|text|好吧，我的答案不仅仅是所有解决方案的总结，它还提供了更多的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341242|部分(1):|offset|length|style|BOLD|341243|通用解决方案中的：|341244|我有4个这样的错误(‘元数据文件找不到’)和一个错误‘源文件不能被打开(’未指明的错误‘)’。|341245|我试图摆脱‘元数据文件找不到’的错误。为此，我阅读了许多帖子、博客等，发现这些解决方案可能是有效的(在这里总结它们)：|341246|341247|重新启动VS并再次尝试生成。|ordered-list-item|341248|转到‘解决方案资源管理器’。右键单击解决方案。转到属性。转到“配置管理器”。检查是否选中了'Build'下的复选框。如果其中任何一个或全部未选中，则选中它们并尝试重新构建。|341249|如果上述解决方案不起作用，则按照上述步骤2中提到的顺序进行操作，即使选中了所有复选框，也要取消选中它们，然后再次选中并尝试构建again.|341250|Build顺序和项目依赖关系：|341251|341252|转到“解决方案资源管理器”。右键单击解决方案。转到‘项目依赖关系...’。您将看到两个选项卡：'Dependencies'和'Build+Order'。此生成顺序是解决方案生成的顺序。检查项目依赖关系和构建顺序，以验证依赖于其他项目(比如“project2”)的某个项目(比如“project1”)是否正在尝试在该项目(project2)之前构建。这可能是导致错误的原因。|341253|Check缺少的.dll的路径：|unordered-list-item|341254|341255|检查缺少的.dll的路径。如果路径包含空格或任何其他无效路径字符，请将其删除，然后重新尝试构建。|341256|如果这是原因，请调整构建顺序。|341257|341258|​|341259|部分(2):|341260|我的特殊情况：|341261|我尝试了上面的所有步骤，使用不同的排列和组合，重新启动VS几次。但是，这对我没有帮助。|341262|因此，我决定摆脱我遇到的其他错误(‘源文件无法打开(’未指明错误‘)’)。|341263|我偶然发现了一个博客：http://www.anujvarma.com/tfs-errorsource-file-could-not-be-opened-unspecified-error/#comment-1539|341264|我尝试了那个博客中提到的步骤，我摆脱了错误‘源文件无法被打开(’未指明的错误‘)’，令人惊讶的是，我也摆脱了其他错误(‘元数据文件无法被找到’)。|341265|341266|部分(3):|341267|故事的寓意：|341268|尝试上面第(1)节提到的所有解决方案(以及任何其他解决方案)以消除错误。如果没有结果，根据上面第(2)节提到的博客，从您的.csproj文件中删除所有源文件的条目，这些条目不再存在于源代码控制和文件系统中。|341269|341270|entityMap|0|LINK|mutability|MUTABLE|url|http://www.anujvarma.com/tfs-errorsource-file-could-not-be-opened-unspecified-error/#comment-1539^0|0|0|6|0|8|1|0|0|0|0|0|2|B|P|2|U|7|19|7|0|0|0|F|0|0|2|B|P|B|1B|E|1Q|D|0|0|G|0|0|0|0|0|0|0|6|0|0|7|0|0|0|B|2P|0|0|L|K|1M|E|0|0|0|6|0|3|3|0|1M|C|0|0^^$0|@$1|2|3|4|5|6|7|23|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|24|8|@$D|25|E|26|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|27|8|@$D|28|E|29|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|2A|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|2B|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|2D|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|2E|8|@$D|2F|E|2G|F|G]|$D|2H|E|2I|F|G]|$D|2J|E|2K|F|G]|$D|2L|E|2M|F|G]]|9|@]|A|$]]|$1|T|3|U|5|Q|7|2N|8|@]|9|@]|A|$]]|$1|V|3|W|5|Q|7|2O|8|@$D|2P|E|2Q|F|G]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2S|8|@$D|2T|E|2U|F|G]|$D|2V|E|2W|F|G]|$D|2X|E|2Y|F|G]|$D|2Z|E|30|F|G]]|9|@]|A|$]]|$1|10|3|11|5|12|7|31|8|@$D|32|E|33|F|G]]|9|@]|A|$]]|$1|13|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|35|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|36|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|37|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|38|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|39|8|@$D|3A|E|3B|F|G]]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3C|8|@$D|3D|E|3E|F|G]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|3H|8|@]|9|@$D|3I|E|3J|1|3K]]|A|$]]|$1|1L|3|1M|5|6|7|3L|8|@$D|3M|E|3N|F|G]|$D|3O|E|3P|F|G]]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|3Q|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3R|8|@$D|3S|E|3T|F|G]]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|3U|8|@$D|3V|E|3W|F|G]]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|3X|8|@$D|3Y|E|3Z|F|G]]|9|@]|A|$]]|$1|1U|3|-4|5|6|7|40|8|@]|9|@]|A|$]]|$1|1V|3|-4|5|6|7|41|8|@]|9|@]|A|$]]]|1W|$1X|$5|1Y|1Z|20|A|$21|22]]]]

Well, my answer is not just the summary of all the solutions, but it offers more than that. 

Section (1):

In general solutions:

I had 4 errors of this kind (‘metadata file could not be found’) along with 1 error saying 'Source File Could Not Be Opened (‘Unspecified error ‘)'.

I tried to get rid of ‘metadata file could not be found’ error. For that, I read many posts, blogs etc and found these solutions may be effective (summarizing them over here):

<ol>
<li>Restart VS and try building again.</li>
<li>Go to 'Solution Explorer'. Right click on Solution. Go to Properties. Go to 'Configuration Manager'. Check if the checkboxes under 'Build' are checked or not. If any or all of them are unchecked, then check them and try building again.</li>
<li>If the above solution(s) do not work, then follow sequence mentioned in step 2 above, and even if all the checkboxes are checked, uncheck them, check again and try to build again.</li>
<li>Build Order and Project Dependencies:

Go to 'Solution Explorer'. Right click on Solution. Go to 'Project Dependencies...'. You will see 2 tabs: 'Dependencies' and 'Build Order'. This build order is the one in which solution builds. Check the project dependencies and the build order to verify if some project (say 'project1') which is dependent on other (say 'project2') is trying to build before that one (project2). This might be the cause for the error. </li>
<li>Check the path of the missing .dll:

Check the path of the missing .dll. If the path contains space or any other invalid path character, remove it and try building again.

If this is the cause, then adjust the build order.

<hr></li>
</ol>

Section (2):

My particular case:

I tried all the steps above with various permutations and combinations with restarting VS few times. But, it did not help me. 

So, I decided to get rid of other error I was coming across ('Source File Could Not Be Opened (‘Unspecified error ‘)'). 

I came across a blog: 
<a href="http://www.anujvarma.com/tfs-errorsource-file-could-not-be-opened-unspecified-error/#comment-1539">http://www.anujvarma.com/tfs-errorsource-file-could-not-be-opened-unspecified-error/#comment-1539</a> 

I tried the steps mentioned in that blog and I got rid of the error 'Source File Could Not Be Opened (‘Unspecified error ‘)' and surprisingly I got rid of other errors (‘metadata file could not be found’) as well.

<hr>

Section (3):

Moral of the story:

Try all solutions as mentioned in section (1) above (and any other solutions) for getting rid of the error. If nothing works out, as per the blog mentioned in section (2) above, delete the entries of all source files which are no longer present in the source control and the file system from your .csproj file. 

<hr>

blocks|key|3325415|text|我自己也有同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325416|Visual+Studio+2013只告诉我它不能引用它，也找不到元数据。当我打开我的解决方案(其中有多个项目)时，它显示我使用的项目比我的一个项目的框架版本低。|3325417|所以我把所有东西都切换到了4.5版，它又能工作了。|3325418|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 had the same problem myself.

Visual Studio 2013 only told me that it couldn't reference to it, and it couldn't find the metadata. When I opened my solution (which has multiple projects in it) it said that I was using projects lower than the framework version of one of my projects.

So I switched everything to version 4.5, and it worked again.

blocks|key|344837|text|我在尝试添加项目引用时遇到了这个问题，经过大量的搜索和尝试，我的构建配置和输出都是正确的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|344838|最后，我从源代码和引用项目中删除了\bin和\obj文件夹。|offset|length|style|BOLD|344839|老实说，我认为是obj文件夹没有包含正确的元数据或损坏的元数据。|CODE|344840|现在一切都解决了。|344841|这是Visual+Studio2015-+.NET+4.6项目的例子。|344842|更新：|344843|上面的方法在第一次构建时有效，但在后续构建中失败了，所以我最终重新创建了解决方案文件，并删除并读取了项目文件中错误引用的NuGet包，这些包指向了错误的提示路径。|344844|到目前为止，这似乎已经在后续的构建中修复了它。|344845|.csproj文件中的示例引用|344846|<ItemGroup>
++++<Reference+Include="Antlr3.Runtime,+Version=3.5.0.2,+Culture=neutral,+PublicKeyToken=eb42632606e9261f,+processorArchitecture=MSIL">
++<SpecificVersion>False</SpecificVersion>
++<HintPath>..\..\packages\Antlr.3.5.0.2\lib\Antlr3.Runtime.dll</HintPath>
++++</Reference>
</ItemGroup>|code-block|syntax|javascript|344847|entityMap^0|0|H|4|M|4|0|8|3|0|0|0|0|3|0|24|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@$D|15|E|16|F|G]|$D|17|E|18|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@$D|1A|E|1B|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1L|8|@]|9|@]|A|$]]|$1|W|3|X|5|Y|7|1M|8|@]|9|@]|A|$Z|10]]|$1|11|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|12|$]]

I was having this issue when trying to add a project reference, and after a lot of searching and trying many of the things above, my build configuration and outputs were correct.
I finally just deleted the \bin and \obj folders from the source and referencing project.
Honestly I believe it was the <code>obj</code> folder not containing the correct metadata or corrupted metadata.
All is fixed now.
This was with Visual Studio 2015 - .NET 4.6 projects.
UPDATE:
The above worked on the first build, but on subsequent builds it failed, so I ended up recreating the solution file, and removing and reading the NuGet packages that were referenced incorrectly in my project files which pointed to the incorrect hint path.
That seemed to have fixed it thus far on subsequent builds.
<h3>A sample reference within a .csproj file</h3>
<pre><code>&lt;ItemGroup&gt;
 &lt;Reference Include=&quot;Antlr3.Runtime, Version=3.5.0.2, Culture=neutral, PublicKeyToken=eb42632606e9261f, processorArchitecture=MSIL&quot;&gt;
 &lt;SpecificVersion&gt;False&lt;/SpecificVersion&gt;
 &lt;HintPath&gt;..\..\packages\Antlr.3.5.0.2\lib\Antlr3.Runtime.dll&lt;/HintPath&gt;
 &lt;/Reference&gt;
&lt;/ItemGroup&gt;
</code></pre>

blocks|key|3325485|text|我也遇到过类似的问题。我删除了类和接口，之后我的构建开始失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325486|3325487|移除所有构建，这样就没有项目构建(配置管理器)|ordered-list-item|3325488|检查构建顺序(截图并将其放入Paint+:d)|3325489|逐个启用并在每次清理、重建和构建时执行。|3325490|现在您知道失败的项目。:-)|3325491|3325492|在我的情况下，我有一个文件夹，里面有一个界面。发生的事情是我注释掉了(FooSolution.StupidProject.Interfaces.IUnicorns)，的接口IUnicorns，这样它就不会再被使用了。没有其他项目再使用IUnicorn了。一切都很好。|3325493|然而..。其他一些项目仍然将using语句添加到该文件夹：|3325494|using+FooSolution.StupidProject.Interfaces|code-block|syntax|javascript|3325495|解决方案：|offset|length|style|BOLD|3325496|3325497|不是像这样注释界面，|3325498|3325499|//公共接口IUnicorn+{|3325500|我还注释了接口上方的名称空间，如下所示：|3325501|//+namespace+FooSolution.StupidProject.Interfaces
//{
//+++public+interface+IUnicorn+{|3325502|我搜索了我的其他项目，确保不再使用namespace!|3325503|Clean+|unordered-list-item|3325504|和一杯好咖啡;-)|3325505|3325506|3325507|结论：检查您在其他项目中的使用情况。|3325508|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|5|0|0|0|0|0|0|0|0|0|0|0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1R|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|1S|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|1T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1V|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1X|8|@]|9|@]|A|$T|U]]|$1|V|3|W|5|6|7|1Y|8|@$X|1Z|Y|20|Z|10]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|12|3|13|5|E|7|22|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|24|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|25|8|@]|9|@]|A|$]]|$1|19|3|1A|5|S|7|26|8|@]|9|@]|A|$T|U]]|$1|1B|3|1C|5|6|7|27|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|1F|7|28|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|E|7|29|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|1J|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|2C|8|@$X|2D|Y|2E|Z|10]]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]]|1N|$]]

I had a similar problem. I removed classes and an interface and after this my builds started to fail.

<ol>
<li>remove all builds so that no project builds (configuration manager)</li>
<li>check the build order (take a screenshot and put it in Paint :D)</li>
<li>enable one by one and do each time Clean &amp; Rebuild and build.</li>
<li>Now you know the project that failed. :-)</li>
</ol>

In my situation I had a Folder with one interface inside.
e.g. FooSolution.StupidProject.Interfaces
What happened is that I commented out the interface IUnicorns (FooSolution.StupidProject.Interfaces.IUnicorns), so that it would not be used anymore.
No other project had IUnicorn in use anymore. Everything was fine.

However... 
some other projects were still having using statements to that folder:

<pre><code>using FooSolution.StupidProject.Interfaces
</code></pre>

Solution:

<ol>
<li>Instead of commenting the interface like,

//public interface IUnicorn {</li>
</ol>

I commented also the namespace above the interface, like this:

<pre><code>// namespace FooSolution.StupidProject.Interfaces
//{
// public interface IUnicorn {
</code></pre>

<ol start="2">
<li>I searched my other projects and made sure there was no using anymore to that namespace!</li>
<li>Clean and rebuild and a good coffee ;-)</li>
</ol>

Conclusion: 
check your usings in other projects.

blocks|key|3325510|text|以管理员身份重新打开Visual+Studio。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325511|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|$]]

Re-open Visual Studio as Administrator.

blocks|key|342386|text|第30个答案:-)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|342387|在VS2015中：|342388|342389|右键单击Solution|unordered-list-item|342390|Select项目生成顺序|342391|查看项目生成顺序中的项目列表|342392|按该顺序生成每个项目|342393|检查输出代码<|342394|>F211|342395|在我的例子中，一步一步地做有助于发现我的问题所在，而没有所有那些左右抛出的错误。|342396|如果你一定要知道，当项目设置为.NET+4.5.2时，我通过NuGet添加了实体框架(EF)+6.1.3。我后来将.NET框架降级到4级，然后错误就更明显了。通过NuGet，我卸载了EF，并重新添加了它。|342397|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|13|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|14|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|17|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|W|$]]

The ~30th answer :-)

In VS2015:

<ul>
<li>Right-click on Solution</li>
<li>Select Project Build Order</li>
<li>Look at the list of projects in Project Build Order</li>
<li>Build each of your projects in that order</li>
<li>Inspect the Output</li>
</ul>

In my case, doing it step-by-step helped discovered what my problem is without all those errors thrown left and right. 

If you had to know, I added Entity Framework (EF) 6.1.3 via NuGet when the project was set for .NET 4.5.2. I later downgraded the .NET Framework down to 4, and then the error was more obvious. Via NuGet, I uninstalled EF and re-added it.

blocks|key|342406|text|在VS+2015中，删除'References‘下的’Analyzer‘解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|342407|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|$]]

In VS 2015, removing 'Analyzers' under 'References' solved the issue

blocks|key|3112730|text|对我来说，通常是目标框架关闭(4.5.2而不是4.6)如果您修复项目的目标框架以匹配解决方案和构建的目标框架，则会创建一个新的.dll。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3112731|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|$]]

For me it's usually the target framework being off (4.5.2 instead of 4.6) If you fix the target framework of the project to match the target framework of the solution and build, a new .dll will be created.

blocks|key|3325619|text|我有这个问题，花了很长时间才弄清楚。当我从解决方案中删除项目并将其替换为nuget包时，出现了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325620|解决方案看起来不错，但.csproj文件仍然多次包含这些项目作为参考。|3325621|似乎VS没有适当地清理该文件。它仍然引用引擎盖下被移除的项目。当手动删除csproj文件中的引用时，所有的引用都会再次工作！哇哦|3325622|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 had this problem and took long while to figure it out. Problem came up when I removed projects from solution and replaced those with nuget packages. 

Solution seemed to be fine but the .csproj file still contained those projects multiple times as reference.

Seems that VS does not clean that file appropriately. It was still referencing the removed projects under the hood. When manually removed the references from csproj file all works again! wohoo

blocks|key|3112782|text|大多数软件都说您需要删除解决方案的库，这是正确的，但当您重新添加库时，错误将再次显示。您需要验证引用的所有库是否都具有与您的解决方案的.net框架兼容的.net框架。然后修复代码中的所有错误并重新生成解决方案。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3112783|entityMap^0|17|14|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Most of the answares say that you need to remove the libraries of your solution, this is true but when you re-add the libraries the error will be shown again. You need to verify if all the libraries referenced have a compatible .net framework with the .net framework of your solution. Then fix all the errors in your code and rebuild the solution.

blocks|key|342438|text|检查项目根目录下的.vs文件夹是否被隐藏。我的不是(也应该是)，因为我从另一台pc进行了复制/粘贴。删除它解决了问题，Visual+Studio+2015刚刚为我重新创建了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|342439|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|$]]

Check wether the .vs folder in the project root is hidden or not. Mine wasn't (and it should) since I did a copy/paste from another pc. Deleting it solved the problem, Visual Studio 2015 just recreated it for me.

blocks|key|3325667|text|对我来说，移除/删除整个.vs文件夹(这是一个看不见的文件夹)，然后：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325668|-+Build
-+Rebuild+|code-block|syntax|javascript|3325669|完成了。|3325670|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|$]]

For me was to remove/delete entire .vs folder(that is an invisible one) and then:

<pre><code>- Build
- Rebuild 
</code></pre>

and done.

blocks|key|341486|text|我也有同样的问题，之前提供的答案都没有解决它。显然，这可能是.csproj文件的问题。由于某些原因，对文件的引用仍然“缺失”，这些文件甚至没有在我的代码中出现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|341487|使用文本编辑器打开您的.csproj文件，查找丢失的文件，然后删除、保存并保存。|341488|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|$]]

I had the same issue, non of the provided answers fixed it before. Apparently this could be a problem with the .csproj file. For some reason the references to files that were not even made anywhere in my code were still "missing". 

Open your .csproj file with a text editor and look for the files missing, delete, save and be happy.

blocks|key|3325696|text|在我的例子中，我是在master的一个分支上工作。所以我签出了主分支，运行了一个构建，然后签出了我的分支。它修复了这个问题。如果您已经在master上，我建议您检查以前的提交，然后构建它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3325697|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|$]]

in my case i was working on a branch off master. so i checked out master branch, ran a build and then checked out my branch. It fixed the issue. If you already are on master, i suggest you check out previous commit and then build it.

blocks|key|340094|text|对我来说，我使用EntityFramework.6.2.0更新到EntityFramework.6.4.0，然后问题就解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|340095|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|$]]

For me, I was using EntityFramework.6.2.0
Updated to EntityFramework.6.4.0 then problem is solved.

Recently I started to get this message randomly:

<blockquote>
 Metadata file '...\Release\project.dll' could not be found in Visual Studio
</blockquote>

I have a solution with several projects in it. The current build mode is Debug and all projects' configurations are set to Debug. But when I try to run the main project - sometimes it gives me a few errors, all of which are "Metadata file '...\Release\projectX.dll' could not be found" - and, look, it says about RELEASE folder, though current mode is Debug. Why? I tried to search for reference to "Release\projectX.dll" inside all solution files, and I found one in ResolveAssemblyReference.cache file.

I made a good search over the Internet and found a few people with a similar problem, but there was no solution, or at least no working solution.

I tried to delete references to those projects and read them, but in some time I start getting these errors again.

It seems like a bug. Why does it search for referenced projects in Release folders when I always use Debug mode?

PS. For those who met this problem: I couldn't solve it in an easy way. It disappeared only after I reinstalled Windows :(

Error "Metadata file '...\Release\project.dll' could not be found in Visual Studio"

代码生成工具

Visual Studio

单元测试

文件系统

包管理器

数据库

编译器

调试器

Windows

最近，我开始随机收到这条消息：在Visual Studio中找不到元数据文件‘...\Release\project.dll我有一个包含几个项目的解决方案。当前生成模式为Debug，并且所有项目的配置都设置为Debug。但是，当我尝试运行主项目时-有时会出现一些错误，所有的错误都是“元数据文件'...\Release\...

问错误“在Visual Studio中找不到元数据文件'...\Release\project.dll‘”
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误“在Visual Studio中找不到元数据文件'...\Release\project.dll‘”EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误“在Visual Studio中找不到元数据文件'...\Release\project.dll‘”
EN