I meant private fields. I use an underscore, but FXcop is complaining.
As far as I can remember FxCop has never fired on private field's naming. We validate code against the
.NET Framework Design Guidelines and the guidelines have never talked about internals; this has always been up to the decision of the developers.
No, but when I've been a v- prefixing with underscores is caught by another internal tool and it's caused interesting, heated discussions.
Ah yes, I know what tool you are talking about. This is soon to be completely replaced with FxCop and there are no intentions to check the name of internals.