.NET Compiler Platform ("Roslyn"): Analyzers and the Rise of Code-Aware Libraries

Download this episode

Download Video

Download captions

Download Captions

Description

We've rewritten (and open sourced!) the C# and VB compilers, and exposed their functionality through APIs as the .NET Compiler Platform. But what do these APIs mean for those who aren't compiler jocks?

Learn about diagnostic analyzers, a key new feature of Visual Studio 2015 that lets a NuGet package introduce custom warnings and errors to your build. Analyzers let a NuGet package easily introduce custom warnings and errors to your build, along with automatic fixes in the IDE. We'll walk through the thought process and development of a simple diagnostic and code fix for the Regex API to see what it's like to quickly build analyzers for an API.

For more information, check out this course on Microsoft Virtual Academy:

Day:

1

Embed

Format

Available formats for this video:

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

    The Discussion

    • User profile image
      Residentx

      Hi Mr. Green,

      I enjoyed your session this morning. My first request. Microsoft has said numerous times that F# would be a first class citizen in the framework. This is another voice encouraging you to remember that promise. Also, nice save enforcing your will on other developers in less than a minute :)

      Second, Legacy of the Void is looking very good. Have you seen the latest Beta release, https://www.youtube.com/watch?v=jCj401zTugk ?

    • User profile image
      GuardRex

      Excellent presentation! Anthony, why haven't we seen more of you at events explaining complicated compiler subjects?

      You made Analyzers very accessible here. I won't be building them, but I sure will be consuming them. I found it easy to understand the value and use of this great tooling. Thanks for a great talk ... one of the best talks at the conference.

      Hope we get to hear from you again at Build and/or TechEd!

    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.