Compartir a través de

What's coming up for C# beyond Whidbey?

  • Artículo

Diego asks,

Now that C# 2.0 is almost here, I'd like to know about features that were left out from this release and planned for the future?

I can't think of anything that I'd say was “left out“. There are a few things that we've been talking about

There are a few things that we've been talking about. Unfortunately, I don't think I can talk about them now.

The basic problem is one of expectation. When we first start talking about something, we're always in the exploratory phase. That's a long way from the “already implemented“ phase when we usually start talking about features.

[Update: Marshall asks whether E&C was left out, or just postponed. Refactoring rated higher than E&C, but we do understand the utility that E&C brings, and we also have gotten a lot of customer feedback in that area. Oh, and to the best of my knowledge, the VB version of E&C does not support web apps. ]

[Update: Mike asks about delays in Whidbey. While I generally know when we have slipped our schedules, I don't track when (or wheter) we've communicated those slips, so I'm going to avoid those sorts of topics. ]

Comments

  • Anonymous
    March 11, 2004
    Was Edit and Continue "Left Out", apparently in favour of Refactoring, or just postponed? This is my biggest gripe when debugging large ASP.NET apps when there are very simple code issues that could benefit from E&C.
  • Anonymous
    March 11, 2004
    The comment has been removed
  • Anonymous
    March 11, 2004
    It seems to now be official that Whidbey has been delayed according to <a href="http://www.eweek.com/article2/0,1759,1546526,00.asp"> this website </a>
  • Anonymous
    March 11, 2004
    If this is due to delays in Yukon, this is just sad. I could't care less about when sql-server is released. (In relation to whidbey.) Some products don't even use a db. Our products have to suport multiple databases and versions. Also, our customers certainly won't upgrade to yukon the first day it is available. We (where I work) however, will release new versions of our products when whidbey is out of the beta-phase. MS have just delayed our schedule due to a product our customers most probably won't consider. Whoever it was who had the insane idea that we should wait for a upgrade of a database to be able to use the latest and greatest IDE & runtime environment should have his/her brain checked. This is in deed sad news.
  • Anonymous
    March 11, 2004
    The comment has been removed
  • Anonymous
    March 11, 2004
    The comment has been removed
  • Anonymous
    March 12, 2004
    If Edit and Continue were the only new feature added, I would be completely satisfied. :-)
  • Anonymous
    March 12, 2004
    > Refactoring rated higher than E&C

    I sometimes wonder who Microsoft ask for these opinions. I suspect it's internal Microsoft developers and Wintellect/DevelopMentor trainers.

    With all due respect, these type of people are not your average C# programmer. In the 3.5 years I've been coding in C#, I've yet to work with anyone who wasn't bothered about E&C.

    I can purchase an exceptionally good C# Refactoring tool from a 3rd party company, but I can't buy C# E&C from a 3rd party. I don't doubt that refactoring is good and a cool feature (I own a 3rd party C# refactoring tool) but E&C is unequivically more important.

    To quote Brian Harry talking about E&C:
    "We are going to ship this product and we will fix this, add this feature back the first thing after we ship v1."
    - August 2001

    Most developers I spoke to were a little upset by this, but could settle for a v1.1 product which had E&C. Sigh.
  • Anonymous
    March 12, 2004
    What about non-null reference types?

    This MSR paper has detailed information:
    http://research.microsoft.com/~maf/Papers/non-null.pdf
  • Anonymous
    April 18, 2004
    I would've voted for Edit/Continue because a good portion of the time I can make a small fix even with the Command Window to just fix that dumb little bug of setting something to 0 instead of 1 for example...

    And suspending .Net 2.0 for Yukon is just plain silly.
  • Anonymous
    April 18, 2004
    Another thing, since supposedly E&C works in VB, why would it require so much effort to get C#'s since it most likely was more of a Runtime issue to relink and graft that code in memory in place of the old IL?
  • Anonymous
    December 18, 2004
    Helpful For MBA Fans.
  • Anonymous
    June 08, 2009
    PingBack from http://insomniacuresite.info/story.php?id=3786