Udostępnij za pośrednictwem


Do you miss 'Edit-and-Continue'?

I do. I loved the 'Edit-and-Continue' feature in Visual Basic 6.0. My C fill in the blank friends tell me that's because I write buggy code but I don't really care. I know one thing - I used it and I liked it. I'm glad that Microsoft plans to add this feature for ALL languages in the next major release of the .NET Framework.

If you are not familiar with 'Edit-and-Continue' then you don't even know what you are missing. 'Edit-and-Continue' allows a developer to launch their application in debug mode, encounter an error (or breakpoint, etc.), edit the offending code, and continue executing the application (in most cases). Very nifty for people who write code with the occasional error.

Do you miss 'Edit-and-Continue'? Is it a waste of Microsoft's time to add back into the IDE/language/framework?

Comments

  • Anonymous
    February 05, 2003
    I'm with you I miss it dearly.
  • Anonymous
    February 06, 2003
    The comment has been removed
  • Anonymous
    February 06, 2003
    Great to see that as a solution for next version. I hope that this new version will not take ages to come on our systems.

    It's actually quite strange that sometime the debugger lock also a simple aspx page, I mean the HTMl part, so you can't edit it. I am not sure how to reproduce that in details, but it happens many time.

    By the way Alex, can you also see if they can improve a little bit the treeview of the objects in debugging mode. I found many times difficult to search for a value in a specific attributes(especially when you don't know th name of what you search for!) in a tre view that can expand to almost infinity !

    Indeed I am not really sure how to fix that ;-)

    Couldn't be cool also to have also the controls as they should rendered in Design mode in VB. In debugging mode so that if you want to change something in a control you don't have to open the control, but eventually modify it in the page and saved automatically.
    Well maybe its some sci-fi but why not !
  • Anonymous
    February 06, 2003
    Errors? ;-)
  • Anonymous
    February 09, 2003
    Yes. This really was a great feature.
  • Anonymous
    May 01, 2003
    I actually prefer VB6 still because it has edit & continue. I used it constantly. Now one little typo and I have to stop (10 seconds), find the code page (5 seconds), fix the error (5 seconds), recompile (5 seconds), and finally get back to that same point the the app (5-30 seconds). (Aslo note: usually while .NET is recompiling, I get bored and start surfing the web--another productivity killer)

    In VB6 I can fix it all in 5 seconds versus 30 seconds to a minute or more in .NET.

    I wish there was a VB 6.5 that had some of the cool stuff of .NET without the slowness and lack of editing in the debugger. I want my instant gratification back!
  • Anonymous
    June 11, 2003
    Edit and continue was also great for just testing things out. I also have the bad habit of surfing while I wait for a compile (That's how I found this page...)
  • Anonymous
    August 25, 2003
    The comment has been removed
  • Anonymous
    November 21, 2003
    Yes! Like everyone already said. It saves time and is more relaxing.
  • Anonymous
    July 20, 2004
    I loved edit and continue, why wasn't it included in the .Net release. What a mistake
  • Anonymous
    July 30, 2004

    Yes! That's how I found this page and I am so dissapointed to know that .net doesn't support this. They are supposed to add features not taking features away.