Tips for Making C# coding Faster and Standard

Here are a few guidelines which I try to stick to in my own coding:

1. Method names should start with an upper case letter and parameter names with a lower case letter. For preference, method names should be verbs rather than nouns.

Try to keep the amount of code within the method to what you can see without scrolling.

2. C# doesn't have functions as such.

3. Prefer the C# aliases for the basic data types (int, double, bool etc.) to their .NET framework equivalents (System.Int32, System.Double, System.Boolean etc.).

Class, struct, interface, enum and delegate names should start with an upper case letter.

4. Where feasible prefer 'switch' statements to if/else if/else ladders.

Prefer the ternary operator (?:) to very simple if/else statements.

5. Property names should start with an upper case letter. For preference, property names should be nouns rather than verbs.

Prefer properties to public fields.

Use automatic properties where feasible to reduce code bloat.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Vulpes13y ago
Accepted answer
Here are a few guidelines which I try to stick to in my own coding:

1. Method names should start with an upper case letter and parameter names with a lower case letter. For preference, method names should be verbs rather than nouns.

Try to keep the amount of code within the method to what you can see without scrolling.

2. C# doesn't have functions as such.

3. Prefer the C# aliases for the basic data types (int, double, bool etc.) to their .NET framework equivalents (System.Int32, System.Double, System.Boolean etc.).

Class, struct, interface, enum and delegate names should start with an upper case letter.

4. Where feasible prefer 'switch' statements to if/else if/else ladders.

Prefer the ternary operator (?:) to very simple if/else statements.

5. Property names should start with an upper case letter. For preference, property names should be nouns rather than verbs.

Prefer properties to public fields.

Use automatic properties where feasible to reduce code bloat.