C# Language Features beyond Whidbey

Diego Mijelshon  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.

We are primarily focused on getting Whidbey polished and out the door right now, so there isn't a lot of thought about features beyond Whidbey right now. Even when we do get into that mode, I probably won't be talking about it.

One of the reasons that we don't like to talk about things when their in the investigative phase is that they are very preliminary. If I said, for example, that we were thinking about adding parallelizing capabilities to C#, then that would be likely to set up an expectation. It might turn out that we weren't able to do that, perhaps because there wasn't a good way to design it, we didn't have time to build it, one of the teams that we were collaborating with changed their focus or schedule, or a multitude of other possible reasons.

Traditionally, we've been fairly binary on this - we don't talk about things until they're already implemented and tested, even if it's fairly sure that we're doing them. We are trying to figure out how to be a little more open in that area.


Comments (9)

  1. Diego Mijelshon says:


    Thanks for your answer.

    While I completely understand your position, I

    was thinking about the kind of stuff you find in Microsoft Research, such as http://research.microsoft.com/~nick/polyphony/intro.htm, or things like Xen…

    Obviously, everyone wants to add his own extensions to C#, but since that’s not gonna happen, it would be nice to know which ones you are actually considering, even if you have to put a red H1 disclaimer about them.

  2. If you’re talking about Microsoft press releases or something, yeah, probably not to say anything expectation-raising. But if you write a blog entry that’s all hedged about with disclaimers, I suspect most people are going to be pretty reasonable when it fails to map closely to reality.

  3. Shawn says:

    woah, where getting polyhponic C#, in 3.0? That’s cool.

    <disclaimer: I’m not a lamer, not a moron, and I’m not serious about this post. I’m only joking. =)) />



  4. You do know that now we’ll expect parallelizing capabilities to be added, right? 😉

  5. moo says:

    I also expect it to put hair on my chest and add 1" to my pecker.

  6. moo says:

    Anonymous methods = bad.

    win.SizeChanged += delegate { win.Text = "My Avalon Window changed"; };

    The call to win.SizeChanged += blah means SUBSCRIBE to this event. Now what been done here is when the debugger steps to the anonymous code block, its confusing, because when i see += operators on events, i think SUBSCRIBE not do this block of code. Its bad bad bad.

    So now I have to think, oh wait, its saying its subscribing, but infact its not when infact the event has fired its now jumping into the SUBSCRIBE code block in the debuber.

    Totally confusing.

  7. Doing things the hard way with RSS Bandit leads to some interesting statistics; Stuff for my Boss and co-workers; SOA and Joe Developer — Phillip gets it right (again); Bits on Reporting Services; Wake up and smell RSS.NET; htmlArea (drool); InfoPath duh; McD’s

Skip to main content