Avoiding FxCop Warning CA0060

July 12, 2011 · 1 min read

Okay, so the title may have been a little misleading. I'm not going to show you how to avoid warning CA0060, but how to avoid your build failing because of this warning.

This is only helpful if you are running FxCop as a Post-build Event. When FxCop fails due to its inability to find indirectly referenced assemblies, it exits with error code 512 (0x200 - Assembly Reference Error). So all you need to do is check that error code, send out a simple warning message, and reset the error code to 0. The following can be placed directly into the Post-build event field in your project's properties.

<YOUR FXCOP COMMAND> IF 512 == %ERRORLEVEL% ( echo postbuildevent:fxcop warning FXCOP:FxCopCode analysis was unable to complete. SET ERRORLEVEL = 0 )

The echo is formatted so that the warning will show up in Visual Studio's Error List. See my other post for more info on how that formatting works here.

This article is part of the GWB Archives. Original Author: blachniet

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.