Setting breakpoints

Is it possible to set breakpoints for every line of code?

Is it possible to know what the first line of code is?  Meaning...when I debug - the first line of code I visit where I can set a breakpoint?

I'm new to MVC and I am wanting to get a better idea of what the code is doing, from the beginning.
Tom KnowltonWeb developerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

käµfm³d 👽Commented:
Not that I'm aware. You can always set a breakpoint at the start of your application and single-step through the code via the F10/F11 keys--the former steps over a line, even if it is a function all; the latter steps into a line, which means if you are at a function call you will proceed into that function's code. With an ASP.NET project it's a bit more difficult to know where execution begins. Once you are running live and you page is rendered in the browser, I would say that putting a breakpoint at the beginning of each action's function body would be cause you to break at the beginning of that execution.
You could right click on the project and go down to debug and then choose step into new instance, that will go to where to program starts and allow you to step through.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
käµfm³d 👽Commented:
While dustock isn't incorrect in what he states, ASP.NET really has two forms of execution:  One is the actual execution of the ASP.NET host application, which is what dustock's example demonstrates, and the other is the processing of an actual request. Technically speaking, the host application is the only thing executing, but when you start thinking about what the client sees/does on your application, then for them execution is the processing of an individual request. This differentiation is what I was referring to above when I said, "it's a bit more difficult to know where execution begins".
Well said kaufmed!
Tom KnowltonWeb developerAuthor Commented:
Thank you both.  : )
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.