Edit and continue

  • Thread starter Thread starter Guest
  • Start date Start date
Will Vsnet IDE and C# ever get "Edit and continue" in the debugger?

Why is this so important? With an interpreted language like VB, E&C is
just a side effect. .NET is a compiled language. That is a much trickier
proposition. I'd much rather have the VS.NET team work on making the
language faster and more stable than obsess over this trifle.

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)
 
It shouldnt be too hard , just rerun the JIT.



Frank Oquendo said:
Why is this so important? With an interpreted language like VB, E&C is
just a side effect. .NET is a compiled language. That is a much trickier
proposition. I'd much rather have the VS.NET team work on making the
language faster and more stable than obsess over this trifle.

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)
 
Frank,

Are you referring to VB6 and before, or VB.NET? If referring to VB.NET,
it should be noted that VB.NET is not interpreted, but rather, it is
compiled into the same format as any other .NET compliant language, which is
intermediate language (IL).
 
Frank Oquendo said:
Why is this so important? With an interpreted language like VB, E&C is
just a side effect. .NET is a compiled language. That is a much trickier
proposition. I'd much rather have the VS.NET team work on making the
language faster and more stable than obsess over this trifle.

From my current understanding, the CLR team has added(or is adding) E&C
support to the systems underpinnings for the whidbey era release, but it is
up to each individual language team to add support into their ide and their
language. Everything I've read has suggested that VB will support it, but
the C# team doesn't consider it something that their customer base needs and
will postpone support for a later release, Orcas or maybe later, hopefully
allowing them to put more work into valuable added features(like the fixed
statement in structures, iterators, etc) over a paradigm that the majority
of the community seems to be against.
However, this is not definate or even certainly correct. However if you look
through the PDC CLR presentations, I recall there being atleast one slide
that discusses the changes to the runtime to support edit & continue.

I'll post a reply when I have time to find the slides I was reading.
 
We've certainly had customer requests to have edit & continue in C#, but for
Whidbey, it didn't prioritize as high as some of the other work we wanted to
do, so we chose to focus on other areas for Whidbey.

We do understand the value of the feature, and will be looking to add it in
future versions. Unfortunately, it's not a cheap thing to do, both from a
theoretical standpoint and given our current architecture.


--
Eric Gunnerson

Visit the C# product team at http://www.csharp.net
Eric's blog is at http://blogs.gotdotnet.com/ericgu/

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Eric Gunnerson said:
We've certainly had customer requests to have edit & continue in C#, but for
Whidbey, it didn't prioritize as high as some of the other work we wanted to
do, so we chose to focus on other areas for Whidbey.

We do understand the value of the feature, and will be looking to add it in
future versions. Unfortunately, it's not a cheap thing to do, both from a
theoretical standpoint and given our current architecture.
For the time being, I think thats the best path. I would like to see E&C,
but many other features are of greater importance. The fixed operator in
structs being one of my favorites.
 
if that wasnt arse licking what was

Daniel O'Connell said:
wanted
For the time being, I think thats the best path. I would like to see E&C,
but many other features are of greater importance. The fixed operator in
structs being one of my favorites.
 
Back
Top