What’s Next for C# and VB?

Download this episode

Download Video

Download captions

Download Captions

Description

Visual Studio is a productivity game changer for C# and Visual Basic! The .NET Compiler Platform ("Roslyn") enables many new experiences that will change the way you write and debug code. In this session, we'll talk about new language features, refactoring support, major debugging enhancements, code aware frameworks, and much more!

Day:

4

Code:

DEVi015

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      Shaun Peet

      I really wish Microsoft would just come out and say "As of 20##, Visual Basic will no longer be actively developed" or something like that. In fact, I wish we had a time machine to go back 5 years and they could have said it then. I might be the world's last living VB developer - but I haven't switched because Microsoft keeps saying "VB isn't dead" yet EVERYTHING they do shows evidence to the contrary.

      I was at this conference but didn't attend this session because I knew it was being recorded. But I sure would have been disappointed to see the title of the session and the title of the presentation not matching.

    • User profile image
      RT1138

      @Shaun Peet, I noticed that one of the team who was responsible in part for VB, Lucian Wischik, has left the company (so I read). Saying that, at least they are still talking about it and doing some enhancements. From my experience, as long as MSFT talks about the product, it isn't dead, yet.

    • User profile image
      The Bitland Prince

      Phasing VB out would make me very sad. VB is incredibly productive and I still write lots of code using VB. No VB in .NET Core is one of the worst decisions MS made (and they made a lot of them). I hope they will keep up with their promise to bring VB.NET to Core somewhat later.

    • User profile image
      Mike C

      VB.NET is required to keep C# healthy, and vice-versa. Having two parallel development tracks fosters an internal cross-pollination of ideas that helps keep the languages at the forefront of technology.

      Killing VB.NET would therefore have a negative impact on C#. If you don't use it, fine, but that's not reason enough to get rid of it.

    • User profile image
      Andrei Rinea

      Make VB great again!

    • User profile image
      Sivasankar​Gorantla

      Nice features.. 

    • User profile image
      stahtufiang

      // just stop the : aaaam aaaaa aaaaa aaaammmm aaaaaa. just talk man, is that hard to tell something you had worked on?

    • User profile image
      Oops

      Mmmm this demo did not go too well ...

    • User profile image
      Florian

      I think the syntax in the demo was correct, it just looked like IntelliSense didn't work for dotting into the tuple.

      No offense, but maybe they should have sent someone else to demonstrate the new features because it felt a little bit like he was not entirely confident about what he is talking about. He seems to be not familiar with the tuple syntax, and he didn't have any code snippets to rely on but had to fallback to Git (which didn't really work). Funny thing is: It kind of demonstrated how dependent people have become on things like IntelliSense.

    • User profile image
      vb core

      @
      Shaun Peet

      Back to your C# with beloved semicolons, braces, explicit casting everywhere and overall encrypted syntax.

      VB have syntax for humans, and is perfectly placed between static and dynamic typed worlds, but peoples with small static logic may not understand this.

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.