Break Point Problem

Question

0.00/5 (No votes)

See more:

VB

break point is not hitting in vb.net windows form

Posted 17-Jan-11 1:59am

IndrajitDasgupat

Add a Solution

Comments

Estys 17-Jan-11 8:03am

So, where is your breakpoint?

Prerak Patel 18-Jan-11 4:51am

Is the breakpoint shown as solid brown circle? or is there any warning symbol with your breakpoint?!

4 solutions

Solution 2

Check:

1) Are you running the debug version: top of the screen, it will say Debug or Release. Ensure you are running debug.

2) Use F5 to execute in debugger, not SHIFT+F5

3) Your breakpoint is on a line of executable code that you will reach in a known way. If in doubt, put it at the top of your Click handler (or whatever you are using) and single step through.

Posted 17-Jan-11 2:21am

OriginalGriff

Solution 3

It could be the case of "The breakpoint will not currently be hit."

If so,
1) Close your project. Remove Bin and Obj.
2) Open project. Clean Solution and then rebuild it.

Check here for more[^]

Posted 17-Jan-11 22:47pm

Prerak Patel

Updated 17-Jan-11 22:50pm

v2

Comments

Prerak Patel 18-Jan-11 5:01am

What's wrong with it? It could be the case! Even google returns 124,000 results.

Solution 4

Right click the project name in the Solution Explorer and choose properties. Then choose the Compile tab on the left. Click on the Advanced Compiler Settings.

Hope this could be the problem there.

Posted 17-Jan-11 22:53pm

Kasson

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Accepted Answer · 2011-01-17T02:16:00

Solution 1

Try putting a breakpoint at the first statement in the constructor. If it stops there, the code you set the breakpoint on is never being executed, and if it's not executed, the debugger won't stop there.

Posted 17-Jan-11 2:16am

#realJSOP

Comments

Sergey Alexandrovich Kryukov 17-Jan-11 19:54pm

This is most likely - a 5. But there also a chance that it won't stop on the constructor -- what to do now? :-)

#realJSOP 18-Jan-11 5:30am

Based on the info he hasn't provided, I guess we're going to have to just wait and see.

Sergey Alexandrovich Kryukov 18-Jan-11 21:31pm

:-)