The Future of Visual Basic and C#

Download this episode

Download Video


The Microsoft Managed Languages team has been focused on rebuilding the VB and C# compilers and editing experiences. This effort has paved the way for these languages to continue evolving for many years to come. However, what does that future actually look like? We explore the editing experience, how public APIs may be used to write language-level extensions, as well as new language features.



Session Type:





General Assembly A



Available formats for this video:

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

    The Discussion

    • User profile image

      CodeRush and ReSharper already do all of this. Why not just buy them out instead of re-inventing the wheel? ;)

    • User profile image


      ReSharper and CodeRush, are both using their own proprietary analyzers and refactoring tools which aren't necessarily the fastest and most memory friendly. And they are not able to add new language features to the compiler as well, nor compile C#/VB code into IL.. All they can do is add code inspections and refactoring.

      If you think Roslyn is imitating what ReSharper and CodeRush are doing then you have completely missed the point. These refactoring and code inspections shown here is merely a "sideeffect" of the whole underlying compiler infrastructure now being available to developers.

      If you really want to see what Roslyn can do, then take a look at ASP.NET vNext ( where Roslyn is used to vastly improve compilation since everything can now be done in memory. Its also possible to break existing assemblies apart and create new ones that only contains the types your project is using reducing assembly size and memory footprint. Very cool stuff.

    • User profile image

      @ketankshukla: I'm pretty sure the Visual Studio team isn't terribly keen on outsourcing parts of their core product to the Resharper people.  They have a really good product from a feature perspective (I'm a paid subscriber and use it every day), but they've also managed to build a monster that really negatively affects VS's performance in a number of areas.  Only Microsoft is going to be able to take a holistic view on the whole subject of code inspections and compilation, and build something that retains good performance through the whole UX.  

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.