By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,611 Members | 1,389 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,611 IT Pros & Developers. It's quick & easy.

VB.NET debugging

P: n/a
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
Nov 20 '05 #1
Share this Question
Share on Google+
15 Replies


P: n/a
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.

"Darren Gulliver" <gu************@hotmail.com> wrote in message
news:en**************@TK2MSFTNGP11.phx.gbl...
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

Nov 20 '05 #2

P: n/a
Nice one, thanks, the help files told me edit & continue was not supported

Cheers Rick!
"Rick Mogstad" <ri**@NOSPAM.computetosuit.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
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.
"Darren Gulliver" <gu************@hotmail.com> wrote in message
news:en**************@TK2MSFTNGP11.phx.gbl...
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


Nov 20 '05 #3

P: n/a
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 Gulliver" <gu************@hotmail.com> wrote in message
news:eX**************@TK2MSFTNGP09.phx.gbl...
Nice one, thanks, the help files told me edit & continue was not supported

Cheers Rick!
"Rick Mogstad" <ri**@NOSPAM.computetosuit.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
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.

"Darren Gulliver" <gu************@hotmail.com> wrote in message
news:en**************@TK2MSFTNGP11.phx.gbl...
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



Nov 20 '05 #4

P: n/a
"Darren Gulliver" <gu************@hotmail.com> schrieb
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.


1. I agree
2. I agree
3. I agree

Edit&Continue is said to return in a future version.

see also:

http://msdn.microsoft.com/vstudio/pr...o/roadmap.aspx

--
Armin

Nov 20 '05 #5

P: n/a
Cor
Darren,
Next VB.Net version Microsoft has announced for that.
But you will become soon finding it normal.
Cor
Nov 20 '05 #6

P: n/a
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
Nov 20 '05 #7

P: n/a
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.
"Fergus Cooney" <fi******@tesco.net> wrote in message
news:u%******************@TK2MSFTNGP12.phx.gbl...
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

Nov 20 '05 #8

P: n/a
Hi Rick,

I hear you, bro!!

Regards,
Fergus
Nov 20 '05 #9

P: n/a
"Darren Gulliver" <gu************@hotmail.com> scripsit:
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.


Edit and Continue will be re-introduced in VS.NET Whidbey (2004).

--
Herfried K. Wagner
MVP VB Classic, VB.NET
<http://www.mvps.org/dotnet>
Nov 20 '05 #10

P: n/a
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
"Darren Gulliver" <gu************@hotmail.com> wrote in message
news:en**************@TK2MSFTNGP11.phx.gbl...
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

Nov 20 '05 #11

P: n/a
Neat.
Nov 20 '05 #12

P: n/a
Cool

"Gavin Jacobs" <no********@inhell.net> wrote in message
news:Ok**************@TK2MSFTNGP11.phx.gbl...
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
"Darren Gulliver" <gu************@hotmail.com> wrote in message
news:en**************@TK2MSFTNGP11.phx.gbl...
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


Nov 20 '05 #13

P: n/a
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

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bm************@ID-208219.news.uni-berlin.de...
"Darren Gulliver" <gu************@hotmail.com> scripsit:
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.


Edit and Continue will be re-introduced in VS.NET Whidbey (2004).

--
Herfried K. Wagner
MVP VB Classic, VB.NET
<http://www.mvps.org/dotnet>

Nov 20 '05 #14

P: n/a
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.
Nov 20 '05 #15

P: n/a
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.
Nov 20 '05 #16

This discussion thread is closed

Replies have been disabled for this discussion.