Click here to Skip to main content
Click here to Skip to main content
Technical Blog

Some Best Practices for C# Application Development

, 17 Oct 2010 CPOL
Rate this:
Please Sign up or sign in to vote.
Some C# best coding practices that I learnt over the last few years

imageFew days ago, in one my earlier posts, I discussed about “Some Best Practices for Silverlight Application Development (XAML)” which got a huge hit by my readers. I got a lot of feedback on that too. Someone from the community also suggested that I write some best coding practices on C#. This struck my mind and hence I decided to write some best practices about C# coding here from my past few years of experience.

For the past few years, I learned a lot and tried to share the best of my knowledge to others who are new in the software development field. I contribute this post to those fellow members. Hope, I will get more feedback and/or suggestions here too.

I liked C# programming when I started with .NET technology. I never tried to write code in VB.NET as I decided my career on that. When I was new to this field, I made a lot of mistakes and from those mistakes I learnt more things. There’s a proverb: “Mistakes make you learn more & more…”. My career was one of them. Also there’s a proverb: “There’s no end to learning in life. Each second, a person can learn”. So, if there are any more suggestions, please share those with me. It will help me and others to learn more in a proper way.

One second, there are various posts available on the internet regarding the same topic. If you do a Google, you will get a number of them. But these collections are based on my experiences, those I learnt and thought of sharing.

Let’s stop here and start discussing the Best Coding Practices of C# application development. Here are some of them:

  • Use proper Naming Conventions
    • Always use Camel or Pascal naming format
    • Avoid all uppercase or lowercase names
    • Never use a name which begins with numeric character
    • Always prefer meaningful names for your class, property, method, etc.
    • Never build different names varied by capitalization
    • Don’t use the same name used in .NET Framework
    • Avoid adding prefixes or suffixes for your identifiers
    • Always use “I” as prefix for Interfaces
    • Always add “Exception” as suffix for your custom exception class
    • Never prefix or suffix the class name to its property name
    • Prefix “Is”, “Has” or “Can” for boolean properties
    • Don’t add prefix for your controls
  • Decide between Value Types and Reference Types
  • Always Use Properties instead of public variables
  • Use Nullable data types whenever required
  • Prefer Runtime Constants over Compile time Constants
  • Prefer “is” and “as” operators while casting
  • Prefer string.Format() or StringBuilder for string concatenation
  • Use Conditional attributes when you need them
  • Use ‘0’ (zero) as default value enum value types
  • Chose between Equals() and Equal (==) operator
  • Always prefer the foreach(…) loop
  • Initialize member variables at the time of assignment
  • Initialize static member variables with static constructors
  • Use constructor chaining whenever possible
  • Minimize boxing & unboxing of objects
  • Properly utilize try/catch/finally blocks
  • Catch only that Exception which you can handle
  • Use IDisposable interface
  • Utilize LazyInitializer in most of the cases
  • Split your logic in several small and simple methods
  • Try to use Patterns & Practices like MVP/MVC/MVVM
  • Always prefer DataBinding to populate values in the UI


Read them here:


- Initial Post (20th September, 2010)

- Explanation of points (17th October, 2010) 

         Explanation of those points are published as an Article. Read it from here:

Appreciate some more points if you have to include in this article.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Kunal Chowdhury (@kunal2383)
Team Leader
India India
Kunal Chowdhury is a Microsoft "Windows Platform Development" MVP (Most Valuable Professional), a Codeproject Mentor, Telerik MVP, Nokia Developer Champion, Speaker in various Microsoft events, Author, passionate Blogger and a Software Engineer by profession.
He is currently working in an MNC located in India. He has a very good skill over XAML, C#, Silverlight, Windows Phone, WPF and Windows Store (WinRT) app development. He posts his findings, articles, tutorials in his technical blog and CodeProject.
Technical Blog:
Twitter :
Follow on   Twitter   Google+   LinkedIn

Comments and Discussions

GeneralMy vote of 4 PinmemberAamer Alduais8-May-12 20:14 
SuggestionFew Missed out Pinmemberzenwalker198527-Oct-11 8:05 
GeneralRe: Few Missed out Pinmvpthatraja27-Nov-11 0:01 
GeneralRe: Few Missed out Pinmemberzenwalker198527-Nov-11 3:17 
GeneralRe: Few Missed out Pinmvp_ Kunal Chowdhury _27-Nov-11 3:35 
GeneralRe: Few Missed out Pinmemberzenwalker198527-Nov-11 6:20 
QuestionNot a convention... Pinmemberlewax0030-Sep-11 11:38 
GeneralMy vote of 2 PinmembertheMukesh12322-Oct-10 0:18 
GeneralSome Best Practices for C# Application Development Pinmemberananda_SriLanka19-Oct-10 10:10 
GeneralMy vote of 4 PinmemberRajanCRT18-Oct-10 21:08 
GeneralSome Best Practices for C# Application Development Pinmemberananda_SriLanka18-Oct-10 20:17 
GeneralRe: Some Best Practices for C# Application Development PinmentorKunalChowdhury19-Oct-10 7:22 
GeneralMy vote of 2 PinmemberBernhard Hofmann18-Oct-10 10:39 
AnswerRe: My vote of 2 PinmentorKunalChowdhury18-Oct-10 19:27 
GeneralI hate these kind of lists (no offense intended) PinmemberJason Christian18-Oct-10 9:10 
Simply because they give no basis for the recommendation. All too often I've worked with programmers that "always/never do that" without knowing why - other than it was on some list of things to (not) do. The list would be much more useful if it gave explanations (like the comment on String.Concat).
Effective C# and More Effective C# are two books that have recommendations with really good, clear reasoning behind them. Highly recommended.
AnswerRe: I hate these kind of lists (no offense intended) - Already Published the Explanation PinmentorKunalChowdhury18-Oct-10 9:17 
QuestionPrefer Runtime Constants over Compile time Constants - Why? Pinmemberbennybechp10-Oct-10 21:45 
AnswerRe: Prefer Runtime Constants over Compile time Constants - Why? PinmentorKunalChowdhury17-Oct-10 4:38 
GeneralMy vote of 5 PinmemberAlfredo Blanco5-Oct-10 3:21 
AnswerRe: My vote of 5 PinmentorKunalChowdhury17-Oct-10 4:40 
GeneralGood advises! PinmemberMember 30824871-Oct-10 3:00 
GeneralRe: Good advises! PinmentorKunalChowdhury17-Oct-10 4:41 
GeneralMy vote of 4 PinmemberOwen Blacker29-Sep-10 3:31 
GeneralRe: My vote of 4 PinmentorKunalChowdhury29-Sep-10 5:57 
GeneralRe: My vote of 4 PinmentorKunalChowdhury17-Oct-10 4:42 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.150327.1 | Last Updated 17 Oct 2010
Article Copyright 2010 by Kunal Chowdhury (@kunal2383)
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid