C# Coding Conventions Handbook

C# Coding Standards Manual

Introduction

Purpose

​ Make it clear that the source program and test program written in C# conform to the same specification, so as to achieve consistency and unity, so as to facilitate the later maintenance and change of the program.
   In the life cycle of a software, 80% of the cost is maintenance.Almost no software is maintained by the original developer throughout its entire life cycle;
   coding standards can improve the readability of software and allow programmers to understand new code as quickly and thoroughly as possible.In order to enforce the specification, every software developer must consistently follow the coding specification;
  The main reason for using the unified coding specification is to standardize the structure and coding style of the application so that it is easier to read and understand this code;
  GoodThe coding conventions used in this document make the source code rigorous, readable, and meaningful, consistent with other language conventions, and as intuitive as possible.

Note: The coding standard is to increase the readability of the code, there is no so-called right or wrong, and you don't have to worry about whether it is right or wrong.

Term Definition

1. Pascal nomenclature: Capitalize the first letter of an identifier and the first letter of each word that follows.Pascal case can be used for identifiers of three or more characters.For example: BackColor.
2. Camel nomenclature: Identifiers are lowercase and each subsequent word is capitalized.For example: backColor.
3. Capitalization: All letters in the identifier are capitalized.Use this convention only for identifiers consisting of two or fewer letters.For example: System.IO, System.Web.UI.
4. The specification of the document is divided into three types: [mandatory] [recommended] [reference], indicating the level of specification that needs to be followed
5. Hungarian nomenclature: Hungarian nomenclature is a type of