XML comments can be used for documentation, as mnaveed suggested. For comments in the code itself, focus on making it easy to find out what the different parts of the code does. Put yourself in the mind of someone who sees the code for the first time, has to locate a specific action in the code and find out how it's done (and what's wrong with it ;)). :: Comment what's unusual or complicated, not what is plain and simple. :: Explaining why something is done is often a more useful complement to the code than how it's done. Most of the time the code itself reveals how it's done, but seldom why. Well written code is also a form of documentation. If you choose good variable names, you don't have to write comments that explains what every variable is used for. --- b { font-weight: normal; }
