Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How can I configure a StyleCop+ naming rule, in such a way that my variable name like controlUI, controlHVACTest, etc. gets validated successfully?
For now, since it is not in sampleName format, the StyleCop+ complains about the naming convention.
Also, what is the best way to add custom naming validation rules?
The most convinient way to allow names like
controlUIandcontrolHVACTestis to addUIandHVACinto “Abbreviations” section.Regarding your question about “changing
AaBbtoA*B*” – I’m not sure that I understand what your mean. StyleCop+ naming rules are very flexible indeed, but if you setup your naming template to$(A)$(*)$(A)$(*)(which seems similar to what you were talking about) – it will force all names to have at least two capital letters (that do not follow each other).If you specify your situation a little bit more, I could try to help you setup your naming templates, if possible.