blocks|key|3049735|text|是的，我也遇到过这个问题。尽管我想说的不是这样，但我相信您必须在构建文件中包含所有可传递的依赖项作为引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3049736|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|$]]

Yes, I've had that problem, too. Though I'd love to say otherwise, I believe you must include all transitive dependencies as references in your build file.

blocks|key|3894792|text|实际上，您可以进入Microsoft.CSharp.targets或Microsoft.VisualBasic.targets文件(位于框架目录中，通常是C：\Windows\Microsoft.NETFrameworkv3.5)，并修改csc或vbc任务参数以包括其他引用依赖项。在文件(VB目标，第166行；C#目标，第164行)中，更改：\|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3894793|References="@(ReferencePath)"|code-block|syntax|javascript|3894794|至|3894795|References="@(ReferencePath);@(ReferenceDependencyPaths)"|3894796|这可能会导致其他问题，这取决于事情有多复杂，它可能会使用Visual+Studio+inproc编译器，但这是我在MSBuild中找到的唯一方法。|3894797|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You can actually go into the Microsoft.CSharp.targets or Microsoft.VisualBasic.targets file (located in the framework directory, usually C:\Windows\Microsoft.NET\Framework\v3.5) and modify the csc or vbc task parameters to include additional reference dependencies. In the file (VB targets, line 166; C# targets, line 164) change:\

<pre><code>References="@(ReferencePath)"
</code></pre>

to

<pre><code>References="@(ReferencePath);@(ReferenceDependencyPaths)"
</code></pre>

This might cause other issues depending on how complicated things are and it may play tricks with the Visual Studio inproc compiler, but it's the only way to do it in MSBuild that I've found.

blocks|key|5305629|text|我把Alex+Yakunin的solution和will+also+copy+native+dll's的组合在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5305630|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1425359/how-to-make-msbuild-to-automatically-copy-all-indirect-references-to-output-bin/1431527#1431527|1|https://stackoverflow.com/questions/4625129/linkresource-in-visual-studio-2010/5854230#5854230^0|F|8|0|T|M|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I've combined Alex Yakunin's <a href="https://stackoverflow.com/questions/1425359/how-to-make-msbuild-to-automatically-copy-all-indirect-references-to-output-bin/1431527#1431527">solution</a> with one that will <a href="https://stackoverflow.com/questions/4625129/linkresource-in-visual-studio-2010/5854230#5854230">also copy native dll's</a>.

blocks|key|5305823|text|与使用Visual+Studio构建相比，使用MSBuild+(即命令行、TFS构建和其他工具)构建时的行为有所不同。辅助引用不包括在发送到MSBuild编译任务的引用变量中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5305824|MSBuild提供了几个扩展点来更改引用的解析方式。对于我的一些项目--+I+have+posted+more+info+about+the+background+on+my+blog，我已经成功地使用AfterResolveReference解决了这个问题。|offset|length|5305825|解决方法是将以下代码添加到vbproj或csproj文件中|5305826|++<Target+Name="AfterResolveReferences">
++++
++++<ItemGroup>
+++++<ReferencePath+Include="@(ReferenceDependencyPaths)">
+++++</ReferencePath>
++++</ItemGroup>+
++</Target>|code-block|syntax|javascript|5305827|微软表示，这是Connect上的一个不会修复的问题|5305828|entityMap|0|LINK|mutability|MUTABLE|url|http://www.nsilverbullet.net/2012/02/17/automatically-resolving-secondary-assembly-references-with-msbuild-and-tfs-build/|1|http://connect.microsoft.com/VisualStudio/feedback/details/367782/bug-msbuild-references^0|0|11|1J|0|0|0|0|7|7|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|9|@$D|16|E|17|1|18]]|A|$]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]]]

There is a difference in behavior when building with MSBuild (i.e. command line, TFS Build and other tools) compared to building with Visual Studio. The secondary references are not included in the references variable sent into MSBuild compile tasks.

There are several extension points provided by MSBuild to change how references are to be resolved. I have successfully used AfterResolveReference to fix this issue for some of my projects - <a href="http://www.nsilverbullet.net/2012/02/17/automatically-resolving-secondary-assembly-references-with-msbuild-and-tfs-build/">I have posted more info about the background on my blog</a>.

The workaround is to add the following code into you vbproj or csproj files

<pre><code> &lt;Target Name="AfterResolveReferences"&gt;
 &lt;!-- Redefine referencepath to add dependencyies--&gt;
 &lt;ItemGroup&gt;
 &lt;ReferencePath Include="@(ReferenceDependencyPaths)"&gt;
 &lt;/ReferencePath&gt;
 &lt;/ItemGroup&gt; 
 &lt;/Target&gt;
</code></pre>

Microsoft has stated that this is a won't fix on <a href="http://connect.microsoft.com/VisualStudio/feedback/details/367782/bug-msbuild-references">Connect</a>

blocks|key|780917|text|如果你得到的是一个有向图而不是一个带有“尝试部署dll的不同副本”错误的树，那么AfterResolveReferences方法就会失败。(请参阅How+to+configure+msbuild/MSVC+to+deploy+dependent+files+of+dependent+assemblies)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|780918|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9742746/how-to-configure-msbuild-msvc-to-deploy-dependent-files-of-dependent-assemblies^0|21|27|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]]]]

The AfterResolveReferences method fails if you've got a directed graph not a tree with a "trying to deploy different copies of the dll" error. (cf. <a href="https://stackoverflow.com/questions/9742746/how-to-configure-msbuild-msvc-to-deploy-dependent-files-of-dependent-assemblies">How to configure msbuild/MSVC to deploy dependent files of dependent assemblies</a>)

blocks|key|5305902|text|josant的回答对我来说几乎是有效的；当我尝试这样做时，我在Visual+Studio中不断收到错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5305903|尝试为集成开发环境的进程内编译器设置"References“参数时出现问题。调用COM组件返回错误HRESULT+E_FAIL|offset|length|style|BOLD|5305904|我的问题的解决方案是在ItemGroup上设置一个条件，如下所示：|5305905|<Target+Name="AfterResolveReferences">
++
++<ItemGroup+Condition="+'$(BuildingInsideVisualStudio)'+!=+'true'+">
++++<ReferencePath+Include="@(ReferenceDependencyPaths)"></ReferencePath>
++</ItemGroup>
</Target>|code-block|syntax|javascript|5305906|这导致Visual+Studio完全忽略引用更改，并且构建在本地和构建服务器上都工作得很好。|5305907|entityMap^0|0|0|19|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|X|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

josant's answer almost worked for me; I kept getting an error in Visual Studio when I tried that: 

A problem occurred while trying to set the "References" parameter for the IDE's in-process compiler. Error HRESULT E_FAIL has been returned from a call to a COM component

The solution to my problem was to put a condition on the ItemGroup, like this:

<pre><code>&lt;Target Name="AfterResolveReferences"&gt;
 &lt;!-- Redefine referencepath to add dependencies--&gt;
 &lt;ItemGroup Condition=" '$(BuildingInsideVisualStudio)' != 'true' "&gt;
 &lt;ReferencePath Include="@(ReferenceDependencyPaths)"&gt;&lt;/ReferencePath&gt;
 &lt;/ItemGroup&gt;
&lt;/Target&gt;
</code></pre>

That caused Visual Studio to ignore the reference change completely, and the build works fine locally and on the build server.

I bumped into a strange situation with MSBuild just now. There's a solution which has three projects: LibX, LibY and Exe. Exe references LibX. LibX in its turn references LibY, has some content files, and also references to a third-party library (several pre-built assemblies installed in both GAC and local lib folder). The third-party library is marked as "Copy Local" ("private") and appears in the output of the LibX project, as the LibY's output and LibX's content files do. Now, Exe project's output has LibX project output, content files of the LibX project, LibY project output (coming from LibX), but NO third-party library's assemblies.

Now I worked this around by referencing the third-party library directly in Exe project, but I don't feel this is a "right" solution.

Anyone had this problem before?

MSBuild doesn't pick up references of the referenced project

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我刚刚和MSBuild遇到了一个奇怪的情况。有一个解决方案包含三个项目: LibX、LibY和Exe。Exe引用LibX。LibX反过来引用了LibY，有一些内容文件，还引用了一个第三方库(在GAC和local lib文件夹中安装了几个预先构建的程序集)。第三方库被标记为"Copy Local“(”私有“)，并出现在L...

问MSBuild不会拾取被引用项目的引用
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MSBuild不会拾取被引用项目的引用EN