VB.NET debugging

  • Thread starter Thread starter Rick Mogstad
  • Start date Start date
R

Rick Mogstad

there is a setting in Tools>Options>Debugging>Edit and Continue

It should allow you to turn it on for VB. I dont know if this will do what you want or not.
 
In VB6 you could change your code while in debug. But in VB.NET I'm told it
is read only can this be changed? A bit annoying if you have to keep
stopping the app to make your changes then start it up again to see if it
works.

Regards
Darren
 
Nice one, thanks, the help files told me edit & continue was not supported

Cheers Rick!
 
i checked the box in VS 2002, but i seem to remember having some problems. I havent looked at it
in 2003 (which I only have at home.)
 
Darren,
Next VB.Net version Microsoft has announced for that.
But you will become soon finding it normal.
Cor
 
Hi Darren, Rick.

I've got v2002.

Edit-and-continue doesn't continue execution with the edits. Ity just
allows you to have them ready for the next rebuild. Sometimes you can't even
do the editting.

I believe that proper edit-and-continue-with-edits will be in an IDE near
you soon.

Regards,
Fergus
 
Thats what i thought i had remembered, but I have just gotten used to having to stop and make my
changes when debugging. If they get a decent edit&Continue feature going in a coming version, it
will certainly be welcome.
 
Darren Gulliver said:
In VB6 you could change your code while in debug. But in VB.NET I'm told it
is read only can this be changed? A bit annoying if you have to keep
stopping the app to make your changes then start it up again to see if it
works.
Click to expand...

Edit and Continue will be re-introduced in VS.NET Whidbey (2004).
 
Darren,
There is a work-around that I use frequently. Whenever you are at a
breakpoint, you can use the "Immediate" window to execute any arbitrary line
of code; so: copy the line that doesn't work, edit it in the Immediate
window, execute it in the Immediate window, then drag the "Next Statement"
pointer past the offending line of code and continue with Step Over or
whatever.

Gavin
 
Cool

Gavin Jacobs said:
Darren,
There is a work-around that I use frequently. Whenever you are at a
breakpoint, you can use the "Immediate" window to execute any arbitrary line
of code; so: copy the line that doesn't work, edit it in the Immediate
window, execute it in the Immediate window, then drag the "Next Statement"
pointer past the offending line of code and continue with Step Over or
whatever.

Gavin
Click to expand...
 
Bah,

Just convinced the bosses to upgrade from VB6 to VS.NET 2002 what's it going
to be like next year!
Microsoft please release a service pack for older versions of vs.net for the
edit & continue.

Darren
 
Hi,
Microsoft please release a service pack for older versions of vs.net for the
edit & continue
<<

I do not think MS will do this (at least, they have indicated that it is
Whidbey only).

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.
 
Hi,

Interesting. I'll have to try this.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
Edition ISBN 1-890422-27-4 (391 pages) published February 2002.
 
Back
Top