Absolutely, positively, no Edit and Continue
See Soma's announcement.
VS 2005 supports Edit and Continue for C#.
You asked for it, again and again. So we did it.
It took a heroic effort by the developers, testers, and program managers in C# to make this happen.
Enjoy.
Comments
- Anonymous
October 15, 2004
The comment has been removed - Anonymous
October 15, 2004
Nice job guys!!!!!
As for the unbinding idea...bad idea! Keep it as it is.
Here is a better solution:
1. Make sure the IDEs can co-exist.
2. Make sure that when running an app out of the IDE the correct runtime is used. (applies mainly to ASP.Net, switching IIS manually or using a util is a pain, the IDE should switch it for you).
3. Give developers who buy an IDE the ability to freely download previous versions if they don't have a subscription. For example: you buy VS2005 Pro, you can download the previously released professional versions like VS2003 Pro. Ken. - Anonymous
October 15, 2004
Jay, you guys are heroic indeed! Thanks for listening!
Sincerely,
AguyWhoIsAMortOnMondayEinsteinOnTuesdayElvisOnWednesdayAndCompletelyRandomTheRestOfTheWeek. :-) - Anonymous
October 15, 2004
Well done.
Although IMO prioritizing something so third-party friendly as "refactoring" over a core engine technology like "edit and continue" was always rather.. uh.. foolish.
Anyway, all water under the bridge now! - Anonymous
October 16, 2004
Thank you SO much! - Anonymous
October 18, 2004
Great news, many kudos to your team and the nice idea of MS Feedback Center - Anonymous
October 26, 2004
how about adding the MY namespace from vb.net 2005 now?! please ;) - Anonymous
October 26, 2004
Thanks!! I wanted to switch from VB to C#, but wasn't because E&C was only in VB. Now I can. This actually changes my image of Microsoft. They do listen!
Now.... no one is ever satisfied are they? How abouts getting E&C to work under ASP.NET? Web developers like to be productive too! :) - Anonymous
October 27, 2004
cwillis: Wow, awesome! That's exactly what we hoped. You asked for it, and we responded. The new MS. :-)
We know that the majority of C# developers do at least some of their work on the web. So by not providing Web.NET E&C, we're missing a big chunk of users. There are two reasons we didn't do that in Whidbey:
- Web scenarios are transient. GUI apps typically run for a long time, but web requests are short. So repeating the debugging session is more painful on client than web.
- It's hard. Much harder than E&C for client application. Remember that C# E&C was added very late in the cycle; we had to scale back the feature as much as possible to make it fit the schedule.
Seem reasonable? - Anonymous
October 27, 2004
The comment has been removed - Anonymous
January 30, 2006
I just saw over on JayBaz's blog that we will have Edit and Continue in C#..  At first thought I...