如何在 Visual Studio 的生成后事件中访问生成警告？

Question

General task . My task is to make a build (of a set of C# projects) failed if there exists such DLLs which were not found and thus were not copied to the output folder. It seems that a corresponding warning is not a warning of a compiler, thus I cannot provide a warning code to the "Treat warnings as errors" option in Visual Studio. The workaround I found is to use MsBuild like it is described here . However I still cannot find any solution for building with a Visual Studio .

Question . Is there a way to obtain a build log and especially build warnings in a post-build event in Visual Studio and make the build failed if some exact warnings exist?

What I looked at . Looked here , but suggested macro is not a convinient solution. According to this and this Visual Studio does not save build logs for C# projects.

More specific . I have been asked to provide information about the specific warning which I want to make an error of. This is "MSB3245: Could not resolve this reference. Could not locate the assembly..."

Answer 1

You could check files in AfterBuild target. For example:

<Target Name="AfterBuild">
    <Error Condition="Exists('$(MSBuildProjectDirectory)\bin\Debug\ClassLibrary1.pdb')==false" Text="file not exist"/>
  </Target>

Answer 2

I have been asked to post a conclusion from the discussion of the current question and my company's experience. So here it is.

Answer . There is no way "to access build warnings in a post-build event in Visual Studio " for managed code projects (excluding some very specific cases, see suggestion about TFS ).

Workaround . Currently we use MsBuild to catch warnings and transform them into errors as it is described here . So developers do not have access to this functionality while they use standard Visual Studio (or ReSharper ) build process. However our continuous integration server uses exactly MsBuild and thus it informs us about warnings and errors which we are interested in.

Other considerations .

1. If the "Treat warnings as errors" functionality in MsBuild were introduced, one could utilize it for similar purposes.
2. One could create a special MsBuild task analyzing the references in project files (.csproj) and comparing this refernces with the files copied to the output folder. This task must be injected in every necessary project file.
3. Some components of TFS probably save build logs (not familiar with this).