Recently we've been on a code quality drive and have eliminated all
compilation warnings from our code. To preserve this state, we've turned
'Treat warnings as errors' to 'All' in all our projects (and if only
this could be a solution level setting!).
However, we've now found that warnings produced by Code Analysis DO NOT
get treated as errors even with this flag set - it looks like this is
because the Code Analysis happens after the compilation, and it's
*compiler* warnings that this setting refers to.
It looks like what we need to do is set the Status to Error for all the
Code Analysis rules - is this right, or is there a setting somewhere
that will cause the *build process* to treat code analysis warnings as
errors?
(VS2005 if is relevant)
--
Larry Lard
la*******@googlemail.com
The address is real, but unread - please reply to the group
For VB and C# questions - tell us which version