When editing files, keep new code and changes consistent with the style in the files. For new files, it should conform to the style for that component.
Last, if there's a completely new component, anything that is reasonably broadly accepted is fine.
1. We use Allman style braces, where each brace begins on a new line. Single line statement block must be enclosed in braces.
2. We use the default Visual Studio four spaces indentation.
3. We use _lowerCamelCase starting with underscore (_) for class private fields, use readonly where possible.
4. We use lowerCamelCase with no underscores (_) for method parameters and variables.
5. Static read only field names are writen in capital letters and can use underscores.
6. We use UperCamelCase with no underscores (_) for naming methods.
7. Avoid more than one empty line at any time. For example, do not have two blank lines between members of a type.
8. Avoid spurious free spaces. For example avoid if (someVar == 0)..., where the dots mark the spurious free spaces.
9. We use language keywords instead of BCL types (i.e. int, string, float instead of Int32, String, Single, etc) for both type references as well as method calls (i.e. int.Parse instead of Int32.Parse).
10. The use of var modifier is prohibited in general, to achive (a) not hiding variable types (i.e. var stream = OpenStandardInput()) and (b) understandable code with a fast look.
11. For almost the same reasons with (7) the use of const modifier, region tags and namespaces is prohibited.
12. Avoid the use of constants, methods, interfaces for code that is not used more than once.
13. Use switch when there are three or more cases to compare, otherwise use if.
14. Add author and date comment for the classes you create. Add your name to an existing class only after doing significant changes. For more that 70% content changes remove previous author(s).