[Simen236]

Not so long ago I installed VS 2012 and I quickly noticed something very irritating when debugging in C#. When debugging Windows Forms Applications, I want it to go straight to the code I've written, but it always goes through the InitializeComponent() method. Is there any way I can make the IDE skip this?

[RudiVisser]

What do you mean it "always goes through InitializeComponent()"?

That's a valid step in your application's setup, leading you to your designer code. You can simply Step Over (F1) this if you don't want to go into the method when it breaks.

This post has been edited by RudiVisser: 16 January 2013 - 04:10 AM

[andrewsw]

Create a Breakpoint by right-clicking the line you want to stop at, or by clicking to the far left of the line, then pressing Start will run to the line. Then you can Step Into F11 or Step Over F10 (if you don't want to jump to called procedures/methods).

You can also right-click the line and choose Run to Cursor.

[Skydiver]

Also check you key mappings. You may have installed or inherited one set of key mappings on your old IDE, and you may have installed the default key mappings when you installed VS2012 instead of porting over your old key mappings from your older IDE.

[tlhIn`toq]

SOunds like you could use a few pointer to debugger smarter not harder


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 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
  
  
  
• 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.

This post has been edited by tlhIn`toq: 16 January 2013 - 07:29 AM

[AdamSpeight2008]

The are Attributes you can add to methods so the debugger skips them.

[tlhIn`toq]

AdamSpeight2008, on 16 January 2013 - 04:06 PM, said:

The are Attributes you can add to methods so the debugger skips them.

Such as... for example... listed at some link...
???

[andrewsw]

DebuggerStepThrough