.net - private members naming convention -
in our project use both vb.net , c# code.
now, microsoft seems not recommend using "_" or "m" prefixes private fields (like _backcolor backcolor).
from other part, used visual studio "c# standard" lowercase private field can't applyed in vb.net code, because vb not support distinguishing identifiers case.
what think?
ps.
studying little bit more ms conventions find out microsoft have no public recommendations of private fields naming, can use of desired...
the whole point of standard promote consistency , understanding.
in case because have multiple languages i'd go either "_" or "m" make sure document why you've made decision in 18 months time new hire (or you) doesn't @ code , go "wtf?".
Comments
Post a Comment