edit and continue?

[Sven Erik Matzen]

Does anybody know when these very old and extremely productive feature "Edit
and Continue" will run like it did in VB6? I mean this is what a tool makes
really RAD - fixing while debugging in contrast to spend hours in debugging,
stopping execution, changing 3 lines, building code, debugging again ...
that's really old style programming. In vb I had edit and continue since I
don't know how many years - now it's gone :.-(

I think it should not be too complex to implement this little feature when
having in mind that the jitter is invoked for each procedure not already
compiled. Why not simply compile the source again to IL and let the jitter
compile to native code again? BTW.: in vb6 I was able to change each line
just before executing it; and change and execute it again if it did not
produce my desired result ... that was coool ;)

CU,

Sven

[Éric Moreau]

The next version will include it (code name Whidbey).

--
HTH

Éric Moreau, MCT, MCSD
Conseiller principal / Senior consultant
Concept S2i inc. (www.s2i.com)

"Sven Erik Matzen" <sv*********@ppepro.com> wrote in message
news:eV*************@tk2msftngp13.phx.gbl...

Does anybody know when these very old and extremely productive feature "Edit and Continue" will run like it did in VB6? I mean this is what a tool makes really RAD - fixing while debugging in contrast to spend hours in debugging, stopping execution, changing 3 lines, building code, debugging again ...
that's really old style programming. In vb I had edit and continue since I
don't know how many years - now it's gone :.-(

I think it should not be too complex to implement this little feature when
having in mind that the jitter is invoked for each procedure not already
compiled. Why not simply compile the source again to IL and let the jitter
compile to native code again? BTW.: in vb6 I was able to change each line
just before executing it; and change and execute it again if it did not
produce my desired result ... that was coool ;)

CU,

Sven

[Russ Bishop]

The problem is that you must add support for edit & continue to the runtime
itself, to debugging services, to visual studio, AND if you are doing all
that you really must add support in a way that all the dotnet languages can
use and add the support to C#, J#, etc.

VS.NET 2003 is just a small patch to VS.NET 2002. The real changes, like E&C
are coming in the next version.

-- russ

"Sven Erik Matzen" <sv*********@ppepro.com> wrote in message
news:eV*************@tk2msftngp13.phx.gbl...

Does anybody know when these very old and extremely productive feature "Edit and Continue" will run like it did in VB6? I mean this is what a tool makes really RAD - fixing while debugging in contrast to spend hours in debugging, stopping execution, changing 3 lines, building code, debugging again ...
that's really old style programming. In vb I had edit and continue since I
don't know how many years - now it's gone :.-(

I think it should not be too complex to implement this little feature when
having in mind that the jitter is invoked for each procedure not already
compiled. Why not simply compile the source again to IL and let the jitter
compile to native code again? BTW.: in vb6 I was able to change each line
just before executing it; and change and execute it again if it did not
produce my desired result ... that was coool ;)

CU,

Sven