The Future of C# and Visual Basic

Download this episode

Download Video

Description

Project "Roslyn" is a complete renewal of the C# and Visual Basic compilers, exposing them as full fidelity APIs for everyone to use, and providing a great foundation for evolving the tool experience and the languages themselves. How can you make use of "Roslyn," and what new language features do we have in store? Come and see!

Day:

2

Session Type:

Breakout

Code:

DEV-B345

Room:

Hall 8.1 Room J

Embed

Format

Available formats for this video:

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

    The Discussion

    • User profile image
      Jodo

      I heard there was an interesting article here. Could not find one. I don't watch unknown videos.

    • User profile image
      Bobby

      @ Jondo There are slides, which give you a quick synopsis (look under the video)

    • User profile image
      Laurynas

      Very nice, it's kinda scary - the rate C# evolves - at first it was just a simple Java clone and now it's, imho, top language together with Ruby (and compared to Ruby you get enormous performance benefits, also a big fan of static typing).

    • User profile image
      Phylos

      So now we have "Project Roslyn" being renamed to the "The .NET Compiler Platform". Shouldn't it really be called "The C#/VB Compiler Platform"? I mention this because C# and VB are not the only .NET languages available and F# will still remain the most advanced statically typed language on the .NET platform, even after C# 6.0 is released.

    • User profile image
      Chuck

      Implementing C# in C# and VB in VB seems like a huge amount of duplicate effort considering that the gap between C# and VB is reducing. This also most likely indicates that VB STILL isn't going away any time soon, even though it will offer no real differences from C#. Having languages with different paradigms (F#) in addition to C# compiling to the same common IL (and thereby allowing cross-use) is awesome, but to me another language differing only by syntax (VB) is a waste. My preference would be to implement C# in C# and leave VB essentially unchanged for legacy code maintenance. The Roslyn team could have gotten C# out in half the time, or maybe provided us with a Roslyn F# instead!

    • User profile image
      craigajohns​on

      To the comment above, VB is certainly not a waste, at least for those of us who use it to write clean .NET code day in and day out. I use C# as well but I prefer the way VB code reads and how it clearly communicates the developer's intent.

    • User profile image
      John

      Every release or talk of the future comes with a vocal group of C# devotees moaning and complaining about VB like it's the devil. VB exists because there is still a demand for it. .Net has given the developer a choice in syntax and that in my opinion is good.

    • User profile image
      T D

      J#, C#, B, C, D (what happend to A?), Mocha, JScript and similar languages are of less importance to business people like accountants, analysts, economists, and financial engineers.

      VBA, SQL, DAX, M, VB.NET, VB6 (RAD with C++ performance) are more useful languages to the business world, especially Visual Basic for Applications.

      Add to that Matlab, R, F#, Python, C++ (for performance), EViews, and perhaps also Troll and SAS and you have a decent toolkit do econometrics, stress testing of banks, build economic models, optimize asset portfolios etc.

      Of all these languages, Visual Basic for Applications is the most used one. It often acts as the glue between databases, simultion models in e.g. Matlab, and the preferred workspace for most users, i.e. Excel, where the users want their results to end up (much more flexible than a DataGrid in .NET) and perhaps keep different simulation parameters for the models.

      Should Microsoft keep only three languages in Visual Studio, then I would suggest that they keep C++, VB.NET and F# (in that order). C# adds not much extra value to that mix. Had there been a future for VB6 (RAD tool on top of C++, generating fast native code) then I had perhaps suggested Visual Basic and F# to be the remaining languages. Keep of course C# (RAD tool on top of slower IL code) for maintainace of legacy code;
      ifn't for{religious C# fundamentalist}; // In order to avoid any terror on behalf of the C# taliban community;
      // ifn't == if not;

      Why not another language? Well sure, but that would be assembly language to take full advantage of 80 bit precision and AVX-512. And should Microsoft consider to bundle Intel Math Kernel Libray with Visual Studio that would be really great. For that, I would trade inC# any day of the week.

      // A Kerningham, Ritchie, Stroustrup, and Hejlsberg fan

    • User profile image
      VB6 Programming

      "VBA, SQL, DAX, M, VB.NET, VB6 (RAD with C++ performance) are more useful languages to the business world, especially Visual Basic for Applications."

      True enough. VBA programming and VB6 programming are still widely used, and yet largely ignored by Microsoft.

    • User profile image
      Bring back vb6 programming

      You would think now that Microsoft are sending .Net to the open source wilderness, they would bring back VB6 programming. VB6 and VBA programming are the most useful business languages.


    • User profile image
      vb6isdeadan​dpoor

      vb 6 is dead poor programming language and GARBAGE

    • User profile image
      Free Turbo C to the dissembler

      VBA i.e. VB6 (or VB7 on x64) is very much alive and kicking and used a lot in the financial industry for example. Anyone at Microsoft who uses C#? The Windows team? The Office Team?<br><br>http://channel9.msdn.com/Events/BUILD/BUILD2011/TOOL-816T<br><br>For performance use C++ and HP libraries such as Intel Math Kernal Library<br>Prototyp in Matlab (or possibly R or Python or F#)<br>Integrated with Office using VB6/7 (i.e. VBA)<br><br>In a future far, far away we will, perhaps, get a new garbage collection mechanism in .NET that can be disabled in order to improve memory mangament and hence performance. MSFT Marketing might even be calling it GC#, not to mean GARBAGE C#, although C# for performance purposes possibly could be considered to be GARBAGE.<br><br>Anyone who believes memory managment is difficult, compared to parallel programming or GPU programming using CUDA? Yes performance is of importance, if you do not get that perhaps you are a C# taliban ;-)<br><br>It would be interesting to get your view on Turbo Pascal. Guess why!?!<br><br>On April Fools&#39; Day you get to hear a lot of silly things...<br><br>

    • User profile image
      Suisse

      Have a look at Delphi XE8. Okay before knocking it down have a look at the features with an open mind. I did and it is very powerful and rich. But dont take my word, make your own experiences.

    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.