yaniv Posted April 16, 2003 Posted April 16, 2003 Some thing happend to my app. and breakpoint does't effect the debug, it is just not stopping!!! I tryed to play with the debug settings and didn't find the way to do it. it is working in other solutions. do you have a solution for me? Quote
*Gurus* divil Posted April 16, 2003 *Gurus* Posted April 16, 2003 Have you verified that debugging symbols are turned on in the solution configuration you're using to build it? Have you tried sticking a Stop keyword in the source (VB) to see if that forces it to break? Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
vincentnl Posted April 16, 2003 Posted April 16, 2003 Must sound stupid, but i mention it anyway, have you perhaps put it in release mode ? go to build.. configurationmanager.. and check that it is in debug mode vincent Quote
Heiko Posted April 24, 2003 Posted April 24, 2003 A typical error of me would be to put a breakpoint in a routine that I think would be executed, but in fact it never is. Have you checked that (with a debug.assert(false) or whatever) ? Quote .nerd
Cassio Posted April 24, 2003 Posted April 24, 2003 Place your breakpoint in a point you know for sure will be executed, like the form_load event. Quote Stream of Consciousness (My blog)
yaniv Posted April 24, 2003 Author Posted April 24, 2003 I triyed it too, actually, i puted a lot of breakpoint, all over the code, it doesn't stop!! Quote
*Experts* Nerseus Posted April 24, 2003 *Experts* Posted April 24, 2003 Try switching from Debug to Release, then back to Debug. In Form_Load put the following: Debug.WriteLine("Hello World") When running, open the Output window (ctrl-alt-o) and see if you see the words "Hello World". If not, you're probably not really in Debug mode. -Nerseus Quote "I want to stand as close to the edge as I can without going over. Out on the edge you see all the kinds of things you can't see from the center." - Kurt Vonnegut
jdccr Posted June 9, 2005 Posted June 9, 2005 I have the same problem I have the same problem but I has tried all and I don't get good result... I discovered that if I build all my components I get the ability to debug again, but It's frustrating and tedious and I lost a lot time because I have a lot projects. I need a urgent solution at this problem!!! Try switching from Debug to Release, then back to Debug. In Form_Load put the following: Debug.WriteLine("Hello World") When running, open the Output window (ctrl-alt-o) and see if you see the words "Hello World". If not, you're probably not really in Debug mode. -Nerseus Quote
ALEX_0077 Posted June 9, 2005 Posted June 9, 2005 Unfortunatly, .Net doesn't seem to work like VB 6, were you can just 'run' and it builds for you. You have to build (i usually re-build), to see new changes. I could be wrong tho. Quote Me = 49% Linux, 49% Windows, 2% Hot gas. ...Bite me. My Site: www.RedPierSystems.net -.net, php, AutoCAD VBA, Graphics Design
Leaders snarfblam Posted June 9, 2005 Leaders Posted June 9, 2005 VB .Net, by default, saves all your open documents and builds when you click the "run" button. This behavior can be modified by going to Tools>Options>Environment\Projects and Solutions\. Quote [sIGPIC]e[/sIGPIC]
jdccr Posted June 10, 2005 Posted June 10, 2005 I found a temporary solution I found a temporary solution at my problem, I discovered that if I set three breakpoints in the function/sub the program stops in the first breakpoint. If I set one or two breakpoints the program doesn't stop. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.