No more debugging

  • Thread starter Thread starter Lloyd Sheen
  • Start date Start date
L

Lloyd Sheen

Well it happens again. I hate this IDE. No more debugging. F8 doesn't
work. Setting breakpoints doesn't work. Worked last week. And yes the
project is marked as debug. And yes it was rebuilt.

Code in the form_load cannot be debugged with F8 and well I can't wait for
2005.

Any new ideas on how to fix this would be great.

Lloyd Sheen
 
Lloyd Sheen said:
Well it happens again. I hate this IDE. No more debugging. F8 doesn't
work. Setting breakpoints doesn't work. Worked last week. And yes the
project is marked as debug. And yes it was rebuilt.

Code in the form_load cannot be debugged with F8 and well I can't wait for
2005.

Any new ideas on how to fix this would be great.

Delete your project's "obj" and "bin" folders and recompile the project.
That may help.
 
Thanks for the suggestion but I have tried that as well. In the last year I
have reinstalled this IDE about 5 times to get things back to working. I
have used VB since it's intial release and while I think that the dot.net
platform is great the IDE is not worthy of the framework.

I am now reinstalling. Even the beta of VB.Express is better and has less
problems (that I have seen) than the retail of VS 2003.

Lloyd Sheen
 
Lloyd said:
Well it happens again. I hate this IDE. No more debugging. F8 doesn't
work. Setting breakpoints doesn't work. Worked last week. And yes the
project is marked as debug. And yes it was rebuilt.

Code in the form_load cannot be debugged with F8 and well I can't wait for
2005.

Any new ideas on how to fix this would be great.

Lloyd Sheen

Just to get the obvious stuff out of the way, you didn't accidentally
set the compiler option to 'release' instead of 'debug' right?
 
Lloyd Sheen said:
Thanks for the suggestion but I have tried that as well. In the last year
I have reinstalled this IDE about 5 times to get things back to working.
I have used VB since it's intial release and while I think that the
dot.net platform is great the IDE is not worthy of the framework.

:-(. I never experienced such a problem...
 
No, a reinstall (about the 6th now since first install) fixed the problem.

Thanks
Lloyd Sheen
 
Lloyd Sheen said:
No, a reinstall (about the 6th now since first install) fixed the problem.

Thanks
Lloyd Sheen

I've used .net and then .net2003 a fair bit.
Most working days for about 3 years now.
Admittedly, only on 3 different machines which are all xp pro.
Never seen that problem.
Had to reinstall once but that was down to someone mucking up the whole
machine rather than the IDE.

Only thing I notice is that largish apps tend to load into the IDE rather
slow and when you hit f5 to debug sometimes nothing happens.

I wonder if it's something else going on with your machine is causing the
problems.
Do you perhaps install stuff may break bits or something?
I'm told installing some versions of sage is a good way to break a dotnet
install.
 
Andy O'Neill said:
I've used .net and then .net2003 a fair bit.
Most working days for about 3 years now.
Admittedly, only on 3 different machines which are all xp pro.

Ive seen it before, albeit not 6 times. The ASP.NET debugger gets goofed up a
ll the time though. Ive got someone on the team at least once a month
reinstalling VS to fix it...



--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Empower ASP.NET with IntraWeb
http://www.atozed.com/IntraWeb/
 
Back
Top