[King o' Hertz]

Thank you!

[Braber01]

I'd like to point out a useful statement I think people hardly know about

Debug.WriteLine(Some_String)

is your friend!

[TwoOfDiamonds]

This tutorial is the "awesomest" !

[tlhIn`toq]

This is a great tutorial, but no single tutorial can contain everything.
So here is a list of other good debugging tutorials and resources.

---

Q: I do x and y happens which I didn't expect but I don't know how to figure out why. How do I debug and find my problem?
A:

• Debugging Express - an introduction to debugging in Visual Studio
  
• Debugging video 1: Breakpoints and Local variables
  
• Debugging video 2: Advanced breakpoints
  
• Debugging tutorial
  
• Debugging tips
  
• Debugging in detail
  
• Great debugging tips
  
• It still doesn't work, article
  
• Debugging tools survival guide
  
• Video: Tips & Tricks to use Visual Studio to the fullest
  
• TIP:Expand compound lines to individual actions:
  5 return dataset.Tables[tableName].Columns.Count;
  A condensed line like this makes a lot of assuptions that everything goes right, and gives you nothing to check or debug.
  
  If only for R&D / Debug purposes it can often be advantagous to break down the line
  

  if (dataset != null)
  {
     if (datase.Tables != null)
     {
        if (!string.IsNullOrWhiteSpace(tableName)
        {
           if (dataset.Tables[tableName].Columns != null)
  

  Now you can put a breakpoint on the top line and walk through it with F10 and check every object. You also don't try to manipulate a thing that doesn't yet exist.

---