Can't modify code during runtime anymore?
Author |
Message |
M #1 / 11
|
 Can't modify code during runtime anymore?
I just got the .NET IDE up and running and the first thing I notice is that I cannot modify my VB code during run/debug anymore. Is this the case? Do I need to somehow turn this feature on? Is it no more? Thanks! M
|
Thu, 07 Oct 2004 09:18:19 GMT |
|
 |
Mike Davie #2 / 11
|
 Can't modify code during runtime anymore?
This is correct behaviour Mike MCP
Quote: > I just got the .NET IDE up and running and the first thing I notice is that > I cannot modify my VB code during run/debug anymore. > Is this the case? Do I need to somehow turn this feature on? Is it no > more? > Thanks! > M
|
Thu, 07 Oct 2004 14:50:01 GMT |
|
 |
Brainwav #3 / 11
|
 Can't modify code during runtime anymore?
Quote: > This is correct behaviour > Mike MCP
> > I just got the .NET IDE up and running and the first thing I notice is > that > > I cannot modify my VB code during run/debug anymore. > > Is this the case? Do I need to somehow turn this feature on? Is it no > > more? > > Thanks! > > M
Go to Tools => Options => Debugging => Edit and Continue, and check "Allow me to edit VB files while debugging".
|
Thu, 07 Oct 2004 19:00:52 GMT |
|
 |
M #4 / 11
|
 Can't modify code during runtime anymore?
Brainwave - thanks. However it looks like MS completely removed the 'code on the fly' feature that made VB the unique language that it was (I have to restart my application when I do simple stuff that VB6 took no problem - want to set that variable to 2 instead of 3? - you have to restart the entire application). Why the HELL did they do this? Microsoft has destroyed a key feature that made VB the unique programming language that it was from day one. This REALLY pisses me off.
Quote:
> > This is correct behaviour > > Mike MCP
> > > I just got the .NET IDE up and running and the first thing I notice is > > that > > > I cannot modify my VB code during run/debug anymore. > > > Is this the case? Do I need to somehow turn this feature on? Is it no > > > more? > > > Thanks! > > > M > Go to Tools => Options => Debugging => Edit and Continue, and check "Allow > me to edit VB files while debugging".
|
Fri, 08 Oct 2004 00:24:15 GMT |
|
 |
Shan #5 / 11
|
 Can't modify code during runtime anymore?
I don't like that I can't change code on the fly either, but the trade off of actually running/debugging the executable code is worth the tradeoff. Also, in case you didn't know it, you can change the variable values 'on the fly'. In the command window, simply type a line of code, hit enter, and it will execute. This is how I change values of data. Quote: >-----Original Message----- >Brainwave - thanks. However it looks like MS completely removed the 'code >on the fly' feature that made VB the unique language
that it was (I have to Quote: >restart my application when I do simple stuff that VB6 took no problem - >want to set that variable to 2 instead of 3? - you have to restart the >entire application). >Why the HELL did they do this? >Microsoft has destroyed a key feature that made VB the unique programming >language that it was from day one. This REALLY pisses me off.
message
>> > This is correct behaviour >> > Mike MCP
>> > > I just got the .NET IDE up and running and the
first thing I notice is Quote: >> > that >> > > I cannot modify my VB code during run/debug anymore. >> > > Is this the case? Do I need to somehow turn this feature on? Is it >no >> > > more? >> > > Thanks! >> > > M >> Go to Tools => Options => Debugging => Edit and
Continue, and check "Allow Quote: >> me to edit VB files while debugging". >.
|
Fri, 08 Oct 2004 20:15:45 GMT |
|
 |
M #6 / 11
|
 Can't modify code during runtime anymore?
This was a key feature that set VB apart from all other windows programming languages from day 1. I find it hard to believe that nobody else is infuriated about this. With the 'code on the fly' feature, I was able to develop and debug 5x faster than C++, etc. I don't understand what you mean that the tradeoff of actually running/debugging the exe code is worth the tradeoff - how so? I'm aware that I can change the 'values' on the fly, but not the source code itself (for example, if I'm working on a function that is called regularly and I want to change a constant, or some other aspect of the function, I cannot; what, I'm supposed to waste my time manually setting that value each time the function is called?). The removal of this feature has completely destroyed the 'power' of development for VB - I might as well just program in C++ and C# now that the debugging method is the exact same for those languages... This is infuriating - I want to hear one good reason why this was done, and how it's more efficient, and how removing the ability to code on the fly while my application was running and replace it with C++ style debugging improves my efficiency and both speed and ability to develop. M
Quote: > I don't like that I can't change code on the fly either, > but the trade off of actually running/debugging the > executable code is worth the tradeoff. > Also, in case you didn't know it, you can change the > variable values 'on the fly'. In the command window, > simply type a line of code, hit enter, and it will > execute. This is how I change values of data. > >-----Original Message----- > >Brainwave - thanks. However it looks like MS completely > removed the 'code > >on the fly' feature that made VB the unique language > that it was (I have to > >restart my application when I do simple stuff that VB6 > took no problem - > >want to set that variable to 2 instead of 3? - you have > to restart the > >entire application). > >Why the HELL did they do this? > >Microsoft has destroyed a key feature that made VB the > unique programming > >language that it was from day one. This REALLY pisses > me off.
> message
> >> > This is correct behaviour > >> > Mike MCP
> >> > > I just got the .NET IDE up and running and the > first thing I notice is > >> > that > >> > > I cannot modify my VB code during run/debug > anymore. > >> > > Is this the case? Do I need to somehow turn this > feature on? Is it > >no > >> > > more? > >> > > Thanks! > >> > > M > >> Go to Tools => Options => Debugging => Edit and > Continue, and check "Allow > >> me to edit VB files while debugging". > >.
|
Sat, 09 Oct 2004 00:23:28 GMT |
|
 |
Carlos J. Quinter #7 / 11
|
 Can't modify code during runtime anymore?
This has infuriated most of us but now we are more calmed ;-) People from MS posted some months ago that this decision caused a lot of grief for them but was necessary due to the deadline of the product. Supposedly it will be back in version 2. -- Best regards, Carlos J. Quintero MZ-Tools 3.0 freeware 'all-in-one' Add-In for VB5, VB6 and VBA: Code Templates, Detect dead code, Favorite Procedures, Favorite Projects, External Utilities, XML Documentation, Private Clipboards, Select Case Assistant, Sort Procedures, Collapse Projects, Split/Combine Lines, Open Folder of File, Edit File As Text, MsgBox Assistant, Connect String Assistant and up to 40+ features: www.mztools.com
Quote: > This was a key feature that set VB apart from all other windows programming > languages from day 1. I find it hard to believe that nobody else is > infuriated about this. With the 'code on the fly' feature, I was able to > develop and debug 5x faster than C++, etc. > I don't understand what you mean that the tradeoff of actually > running/debugging the exe code is worth the tradeoff - how so? > I'm aware that I can change the 'values' on the fly, but not the source code > itself (for example, if I'm working on a function that is called regularly > and I want to change a constant, or some other aspect of the function, I > cannot; what, I'm supposed to waste my time manually setting that value each > time the function is called?). > The removal of this feature has completely destroyed the 'power' of > development for VB - I might as well just program in C++ and C# now that the > debugging method is the exact same for those languages... > This is infuriating - I want to hear one good reason why this was done, and > how it's more efficient, and how removing the ability to code on the fly > while my application was running and replace it with C++ style debugging > improves my efficiency and both speed and ability to develop. > M
|
Sat, 09 Oct 2004 00:29:02 GMT |
|
 |
MVP #8 / 11
|
 Can't modify code during runtime anymore?
<snip> Quote: > This is infuriating - I want to hear one good reason why this was > done, and how it's more efficient, and how removing the ability to > code on the fly while my application was running and replace it with > C++ style debugging improves my efficiency and both speed and ability > to develop.
This feature was present in an early beta, however it was not working correctly. . . The fact of the matter is, the difference between VB6 and .NET was significant enough that, from what I understand, MS had to completely rethink the way they were going about implementing this feature. This functionality (formally known as "Break, Edit, and Continue" or BE&C) is on the top of the feature lists for V2, as far as I know. Personally, I am glad that they released when they did versus delaying another month in order to have this feature. . . I have no comments as to whether or not debugging is better with or without it. . . I never used it before and I'll probably never use it when they put it back in. . . . -- Jacob Grass Microsoft .NET MVP
|
Sat, 09 Oct 2004 00:35:54 GMT |
|
 |
Carlos J. Quinter #9 / 11
|
 Can't modify code during runtime anymore?
Quote: > order to have this feature. . . I have no comments as to whether or not > debugging is better with or without it. . . I never used it before and I'll > probably never use it when they put it back in. . . .
Really? That is quite surprising because, IMO, it is one of the best features of our old friend VB6. Without it, the RAD concept remains only on the coding part (very good in VS.NET), but not in the debugging part, which is an important aspect of the development cycle. -- Best regards, Carlos J. Quintero MZ-Tools 3.0 freeware 'all-in-one' Add-In for VB5, VB6 and VBA: Code Templates, Detect dead code, Favorite Procedures, Favorite Projects, External Utilities, XML Documentation, Private Clipboards, Select Case Assistant, Sort Procedures, Collapse Projects, Split/Combine Lines, Open Folder of File, Edit File As Text, MsgBox Assistant, Connect String Assistant and up to 40+ features: www.mztools.com
|
Sat, 09 Oct 2004 15:57:25 GMT |
|
|
|