Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

mads.torgersen

mads.torgersen mads.​torgersen

Niner since 2007

  • Mads Torgersen: Visual Studio Async CTP (SP1 Refresh) Overview

    @mik: Also notice that I use way too many smileys when I write Smiley Smiley Smiley.

  • Mads Torgersen: Visual Studio Async CTP (SP1 Refresh) Overview

    @Borum.NET: This might end up being an uncharacteristic release with just one feature in C#. VB has a few more.

    @aL_: Silverlight and phone versions of TPL (cut down somewhat) are part of the CTP.

    @mik: Awesome feedback. Excellent observation. As someone relatively new to America, I guess I have to make up for it by using those terms five times as much Smiley.

    @Tormod: I have no NUGet experience. But since the CTPs are very temporary and will eventually be integrated into next version of other products, and also since production use is not condoned but only tolerated Smiley it is probably good that we handit out through only one very controlled channel.

    @exoteric: Perf is a major factor in the production version of async. Much of this isn't in the CTP, because we are not replacing the Task type from the .NET framework. So if it lags a little for you, stay tuned for the real thing Smiley.

  • Luca Bolognese: C# and VB.NET Co-Evolution - The Twain Shall Meet

    It doesn't necessarily mean that. Exception filtering is one of those features that there is comparatively low interest in, and so adding it to C# "just because" VB has it may not be the best investment.

    Think of co-evolution not as a mechanical thing but as a framework for decision making. Whenever we add a new feature, all else equal we do it in both languages; if it is valuable enough to add to one, it is most likely also valuable in the other. But literally adding to C# every feature that VB already has, and vice versa, is hardly a good approach, so we have to find a balance. I'd say that exception filtering is right around that balance point, so I can't say for sure one way or the other.

    Thanks,

    Mads Torgersen, C# Language PM