Solved

debugging in Visual Studio 2010

Posted on 2013-05-17
1
595 Views
Last Modified: 2013-05-17
Hi experts,

In Visual Studio 2010 when I'm debugging a Windows Forms application I set a breakpoint on a certain line of code.
Then when click F5 to start debugging the application the application starts up and runs until it hits my line of code where I set my breakpoint.

Once it stops at my breakpoint I can either do one of the following:

click F5 (to Start Debugging again)
click F8 (Step Into)
click Shift + F8 (Step Over)
click Ctrl+Shift+F8 (Step Out)

When I choose either Start Debugging, Step Into, Step Over, Step Out these operations go forward in my application execution.
What I mean is, if I set my breakpoint at line 9, and then click Step Into, then the next line that gets executed is line 10 and then line 11 and so forth.

So my question is this:

Is there a way to set a breakpoint and then Step Into but go backwards?

or

Is there a way to see a list of execution order of certain methods that are run when my application starts up?

See in my windows forms application that i'm testing, when the application is launched,
a login form comes up.
Once you log in, then the application checks your login credentials against a database and if you are successfully validated then you are taken to the main form.

I want to see all the forms or classes that are hit between the time the user enters their credentials and the time the main form launches after validation is successful?
0
Comment
Question by:maqskywalker
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 75

Accepted Solution

by:
käµfm³d   👽 earned 500 total points
ID: 39175868
You cannot step backwards, but you can drag your "next statement to execute" arrow (the little yellow arrow in the left margin) to previous spots in your current block. In order to see order of execution of methods, you can examine the "Stack Trace" window (Debug->Windows->Call Stack / Ctrl-D, C) to see the current stack of methods that were called up to the breakpoint.

Screenshot
0

Featured Post

Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article describes relatively difficult and non-obvious issues that are likely to arise when creating COM class in Visual Studio and deploying it by professional MSI-authoring tools. It is assumed that the reader is already familiar with the cla…
Many of us here at EE write code. Many of us write exceptional code; just as many of us write exception-prone code. As we all should know, exceptions are a mechanism for handling errors which are typically out of our control. From database errors, t…
Although Jacob Bernoulli (1654-1705) has been credited as the creator of "Binomial Distribution Table", Gottfried Leibniz (1646-1716) did his dissertation on the subject in 1666; Leibniz you may recall is the co-inventor of "Calculus" and beat Isaac…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question