The talk will be the better the more active the audience is. Remember, this is the first talk after lunch. So...

Introducing Razor Pages: a bit like ASP.NET Web Pages, but better, i.e. "best of MVC with less ceremony". If you're a borderline PHP developer, do we have some transitional technology for you!

Anatomy of a web application. Not many files.

Demo of the basics of app configuration and stuff. VS 2017 can now edit csproj files without having to unload the project first. The future has arrived.

Taylor is into League of Legends and Pokemon Go. Just sayin'.

Demo of the difference between a standard MVC app and a Razor Pages app. The latter is just add cshtml file, run. No controller, action, Views folder. You can (or rather will be able to in the next version) embed logic otherwise contained in controllers. Looks very neat until you get PHP flashbacks.

Just casually used C# 6 string interpolation. Well, since Roslyn the objectively best programming language in the known universe gets better even faster.

Razor Pages is not obsolating MVC, it's another way to structure your app. Might help newcomers start with ASP.NET. Wonder if this could be used in an Orchard module?

Razor tooling is being redesigned to decouple it from VS, allow extensibility and be able to provide an overall better developer experience like during refactoring.

Their platform had a huge network of dependencies: disabling a feature can disable dozens of others. So they refactored and moved all common central service interface to a common module. Still not perfect, so the next step was to factor those out to smaller projects containing interfaces.

Output caching is handled with Redis too on top of a local in-memory cache.

Scheduled task caused deadlocks in production due to tasks being wrongly rescheduled from multiple nodes. The ultimate solution was to move task execution out to Hangfire (after implementing a workaround of only letting tasks be executed on a single node).