C# Best Practices

BEST PRACTICE 1:

Avoid #region in your code wherever possible

BEST PRACTICE 2:

Remove unused using statements

BEST PRACTICE 3:

Do not use "this" keyword

BEST PRACTICE 4:

Use Resharper

BEST PRACTICE 5:

Make code as readable as possible, not as short as possible

BEST PRACTICE 6:

Don't use singleton. It's an anti-pattern

BEST PRACTICE 7:

Use one file per class with matching name

BEST PRACTICE 8:

Don't depend on external static methods and properties, inject the dependencies instead

BEST PRACTICE 9:

Use parametrized sql queries

BEST PRACTICE 10:

Defensive copies of objects

BEST PRACTICE 11:

Parameter validation

BEST PRACTICE 12:

Non-confusing, descriptiove and self-explanatory variable naming

BEST PRACTICE 13:

Return interfaces instead of concrete types

BEST PRACTICE 14:

Naming of the extension class

BEST PRACTICE 15:

Not too many parameters on a method

BEST PRACTICE 16:

No view models in services

BEST PRACTICE 17:

Any() instead of Count() > 0

BEST PRACTICE 18:

Do not use short variable names

BEST PRACTICE 19:

Explicit implementation of multiple interfaces

BEST PRACTICE 20:

No public initialization methods

BEST PRACTICE 21:

Services should be stateless

BEST PRACTICE 22:

Referencing projects within he same solution

Become a Best practice hero.
Help us to grow the catalogue of best practices.
Submit a best practice

Recently added best practices

Anonymous
flex-box

Anonymous
a

Anonymous
hello

LaceJaguar65
e

Back
to Top

C# Best Practices

Recently added best practices

Comments