我的c#项目需要构建日志文件吗?

我的c#项目需要构建日志文件吗?,c#,visual-studio-2017,C#,Visual Studio 2017,当我在VS2017中构建我的C#Winforms项目时,我得到以下警告 Found conflicts between different versions of the same dependent assembly that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. 我找到了可以使用工具

当我在VS2017中构建我的C#Winforms项目时,我得到以下警告

Found conflicts between different versions of the same dependent assembly 
that could not be resolved.  
These reference conflicts are listed in the build log when log verbosity is 
set to detailed.    
我找到了可以使用工具->选项->项目和解决方案->构建和运行将详细性设置为详细的地方

我真的需要构建文件吗?因为当我更改详细信息时,我会在输出窗口中获得更多信息

如果是,我在哪里找到它

输出窗口状态为

3>Building with tools version "15.0".
3>Project file contains ToolsVersion="12.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="15.0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424.
3>Target "_CheckForInvalidConfigurationAndPlatform" in file "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets" from project "C:\devvm\git\SBD.JobTalk.MyobApi\MYOBAPITests\MYOBAPITests.csproj" (target "BeforeRebuild" depends on it):
3>Task "Error" skipped, due to false condition; ( '$(_InvalidConfigurationError)' == 'true' ) was evaluated as ( '' == 'true' ).
3>Task "Warning" skipped, due to false condition; ( '$(_InvalidConfigurationWarning)' == 'true' ) was evaluated as ( '' == 'true' ).
3>Using "Message" task from assembly "Microsoft.Build.Tasks.Core, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
3>Task "Message"
3>  Configuration=Debug
3>Done executing task "Message".
3>Task "Message"
3>  Platform=AnyCPU
3>Done executing task "Message".
3>Task "Error" skipped, due to false condition; ('$(OutDir)' != '' and !HasTrailingSlash('$(OutDir)')) was evaluated as ('bin\Debug\' != '' and !HasTrailingSlash('bin\Debug\')).
3>Task "Error" skipped, due to false condition; ('$(BaseIntermediateOutputPath)' != '' and !HasTrailingSlash('$(BaseIntermediateOutputPath)')) was evaluated as ('obj\' != '' and !HasTrailingSlash('obj\')).
3>Task "Error" skipped, due to false condition; ('$(IntermediateOutputPath)' != '' and !HasTrailingSlash('$(IntermediateOutputPath)')) was evaluated as ('obj\Debug\' != '' and !HasTrailingSlash('obj\Debug\')).
3>Done building target "_CheckForInvalidConfigurationAndPlatform" in project "MYOBAPITests.csproj".

看看这两篇MSDN文章


看看这两篇MSDN文章


我确实使用输出窗口中的信息解决了我的问题,因此我猜测,如果从IDE中生成日志文件,则无需定位日志文件。也就是说,输出窗口提供的信息与日志文件一样多。

我确实使用输出窗口中的信息解决了我的问题,因此我猜测,如果从IDE中生成日志文件,则无需定位日志文件。也就是说,输出窗口提供了与日志文件一样多的信息。

此链接似乎是针对C++项目的。当从IDE中构建它时,该链接似乎是针对C++项目的,而不是将其输出到日志文件。它仅在从MSBuild或其他命令行生成方法生成时执行。设置中日志文件冗长的原因是C++项目的日志文件。冗长设置也影响C输出窗口。我想我需要长篇大论来解决我的问题。当我回到我的开发pc上时,我会再次检查。默认情况下,从IDE构建时,它不会输出到日志文件。它仅在从MSBuild或其他命令行生成方法生成时执行。设置中日志文件冗长的原因是C++项目的日志文件。冗长设置也影响C输出窗口。我想我需要长篇大论来解决我的问题。当我回到我的开发pc上时,我将再次检查。