You only get this error if you do both of the following:
1) Enable code analysis on the test assembly
2) Include the globalization rules in the analysis
There doesn't seem to be any reason to do that on a test assembly.
Charlie
On Fri, Oct 5, 2012 at 5:10 PM, Mat Kramer <
mek...@gmail.com> wrote:
> In Visual Studio 2012, when I call Assert.That with a literal string as the
> second parameter (message), I get a CA1303 warning suggesting that I pull
> the string from a string table. This really isn't applicable since it's a
> unit test. According to the documentation, this is because the parameter
> name is message. It would be nice if the parameter name could be changed
> (debugMessage?) to avoid this warning. Or is there another attribute that
> should be applied across the board for NUnit so it doesn't trigger
> localization warnings?
>
> Thanks,
>
> -Mat
>
> --
> You received this message because you are subscribed to the Google Groups
> "NUnit-Discuss" group.
> To view this discussion on the web visit
>
https://groups.google.com/d/msg/nunit-discuss/-/zlsgWsLzgs8J.
> To post to this group, send email to
nunit-...@googlegroups.com.
> To unsubscribe from this group, send email to
>
nunit-discus...@googlegroups.com.
> For more options, visit this group at
>
http://groups.google.com/group/nunit-discuss?hl=en.