What's New in C# 6 and Visual Basic 14

The Discussion

• 

  我手上正在使用1020，我很期待WIN10的到来，将来打算入手微软办公平板电脑

• 

  Happy e

• 

  Can an app targeted for older versions of the .NET Framework take advantage of the new features in C# 6/VB 14 (like the nameof operator or the elvis operator)?

• 

  I'm realy excited! I love programming [H]

• 

  @Andre Silva -- yes!

• 

  Slide is broken, cannot open.

• 

  I also cannot open these slides using the Win10 Powerpoint UWP

• 

  The slide is broken

• 

  @Jeff, @AdamMarks2, @7bitex,

  You are right, the slides are broken. I've started to ask around to see if we can get it fixed.

  The "good" news is that there isn't a lot in the slides. Almost the whole session is demo. The only slides with anything interesting in them occur before we start demoing, in the first few minutes of the talk, so you can just watch a few minutes of the video to see them.

  I'll post back here if/when I learn that the slides are fixed.

• 

  Why won't VB get Await in Catch/Finally clauses and expression-bodied members in this release? Especially Await in Catch/Finally, which seems to be only code-related (no design issues). Is implementing Await in Catch/Finally that more difficult or time-demanding in VB than it is in C#?
  Also, can we expect this gap between VB and C# to keep widening in the future?
  I would be happy to see a blog on the future of VB from Microsoft. VB has been left out from a lot of things recently, and that makes me wonder if it's still worth investing on it. I'm already trying to move my main business to C#, but it would be nice to know for sure if I should do that asap or if I still have more time.

• 

  The slide is not able to open.

• 

  The slides have now been updated, and they seem to work, at least for me.

• 

  @Andre,

  We implemented await in catch and finally for C# first. It was exceedingly complicated, and the truth is we ran out of time to do it with high confidence in VB, just as some features also had to be dropped from C# at the last minute for lack of runway to do it well. I expect us to want to do it in the next version of VB.

  For the record, a lot of the VB 14 features actually reduce the gap between VB and C#. Please check out the feature list on GitHub. Many of the new VB features were already in C#.

  Whether to stay with VB or move to C# is ultimately a business decision you'll have to make based on the sum of factors affecting your specific situation. I can say that the value added to VB in VS 2015 is simply astounding: Lots of new language features, completely revamped IDE with refactorings, Roslyn analyzers and fixes, greatly improved debugging, etc., etc. From the core language experience point of view, this is the biggest renewal of VB in a long time.

• 

  @Andre, just to note, lack of await in catch/finally has a very easy workaround. For instance, instead of

  Try
      stuff1
  Catch ex As Exception
      stuff2
      Await r.CloseAsync()
  End Try

  you can instead write

  Dim t As Task = Nothing
  Try
      stuff1
  Catch ex As Exception
      stuff2
      t = r.CloseAsync()
  End Try
  If t IsNot Nothing Then Await t

   

• 

  @MadsTorgersen @ljw1004 Thanks a lot for the replies. And I knew about the workarounds, it's just that after seeing VB being left out from some things recently, I feared (and I still do! :p) for its future.

• 

  harap di normalkan kembali