Author(s):	Justin Rusbatch
Location	Mezzanine
Date	apr Tue 14	Days Raw Files
Start	15:40	First Raw Start	error-in-template
Duration	00:30:00	Offset	None
End	16:10	Last Raw End
Chapters
Total cuts_time	None min.

http://lanyrd.com/2015/dotnetfringe/sdkxmm/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Embellishing_APIs_with_Code_Analyzers.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Learning a new API can be very difficult and documentation is cumbersome to read. Fortunately, there is a new way to guide the users of your library into the Pit of Success. Code Analyzers are a feature of the .NET Compiler Platform that allow you to extend IntelliSense for anyone who installs your library. By implementing your own Code Analyzer you can take advantage of the compiler to alert your callers of mistakes in real-time. And, by also providing a Code Fix, you can even fix their mistakes for them! In this talk I'll show you how you can write Code Analyzers for Visual Studio 2015 and ship them alongside your library in a NuGet package. We'll also take a look at several open source Code Analyzers to see how you can use them to improve the quality of your code. markdown
Comment:	production notes