Good coading practices in developmet in

Good coading practices in developmet in
1. Remove unused private fields and functions.
2. Do not cast unnecessarily. Avoid duplicate casts where possible, since there is a cost associated with them.
3. Properties that return arrays are prone to code inefficiencies. Consider using a collection or making this a method.
4. To test for empty strings, check if String.Length is equal to zero. Constructs such as "".Equals(someString) and String.Empty.Equals(someString) are less efficient than testing the string length. Replace these with checks for someString.Length == 0.
5. Methods in the same type that differ only by return type can be difficult for developers and tools to properly recognize. When extending a type, be sure not to define new methods that differ from base type methods only by type.
6. Use stringbuilder instead of string types for string manipulation.
7. Use String.Format instead of concatenating and appending strings.
8. Use Type.TryParse rather than Convert.ToDestinationType(). For example use int.TryParse() rather than Convert.ToInt32() which might throw an exception.
9. Override Equals() method wherever applicable in your classes.
10. Consider passing base types as parameters - Using base types as parameters to methods improves re-use of these methods if you only use methods & properties from the parameter's base class. E.g. use Stream instead of FileStream as a parameter when only calling Stream.Read(), this makes the method work on all kind of streams instead of just File streams.

No comments: