Home > Net >  Consult: VS2017 controls names and naming rules
Consult: VS2017 controls names and naming rules

Time:09-17

Install VS2017 today and found a stupid question, consult the:
Control, the name is lower case by default, coding standards have been prompted to capitalize the first letter, it is a question of Microsoft? Or I install problem?

Why each manual to change?

CodePudding user response:

The only news, do not affect compilation,
You can turn off such news,
Of course it is better to change my name

CodePudding user response:

You use the mouse to check it just a matter of the news, never care about that, didn't see you this post I didn't know about this thing,

CodePudding user response:

Your vs loading code extensions

CodePudding user response:

No relationship, as long as the binding event at the front desk and the background of the event name

CodePudding user response:

Programmers only care about the error does not care about warming

CodePudding user response:

Tools - options - text editor - named after a c # code style - - the members of the field, only to adjust refactoring, or delete,

CodePudding user response:

Programmers need to be concerned with not only the error more need to be concerned with warming

CodePudding user response:

Basic can need not tube, warnings and messages unless you run into a must according to IBM, BAT, like Google "giant" coding standards, and a day to speak "Code aesthetics" director of Code Review,

CodePudding user response:

Warnning the compiler does not affect, and ignored to drag out the control of default is small, it is best not to use directly, for the general to an identifiable control, or are entirely buttonN, look not scratched? Should be you to add the encoding rules limit
  • Related