I disagree with Winslow, the presenters are just being friendly, and they are.
For the record, I'm thankful for these videos, they're really helping to unravel the mountains of generated junk I now have to try and rework in my new site - no one just starts using templates without making it conform to the ways of your team.
I've never before started an MVC project and then immediately needed to take the day off to watch several videos about all the crap in the template.
I have a general rant here about that:
But specifically about this video, I would really warn against taking the view that "magic" will mean we don't need to know anything.
Quote: "This is just template code, you don't necessarily have to understand what's going on here."
Man. I need to know what that code is doing. Also, it's why I'm watching this video. It's this thinking that's left the template with such a lack of comments, both proper XML comments and tons of prose about what's going on and why. Who reviewed this template?
Please stop being happy about framework magic. It makes us stupid and its not discoverable.
Also, you don't explain Owin within the context of IIS. Although I've followed Owin and Katana for a while, I was under the impression that Owin was an alternative pipeline that was only used when not on IIS. I guess at some point, we have to move across. Are we running two pipelines now? What's the deal? If this is new and the future, and its so important for auth, then it needs more focus.
I think you needed to spend a bit more time in the opening minutes on comparing the old world with the new. How Owin is exposed to and permeates an MVC 5 application today.
There are some odd things going on in the template (no comments of course) like in the ChallengeResult, where it's seemingly having to communicate a response to two pipelines; it reaches down to Owin to send a Challenge and then also returns a traditional response message. It's odd.
I'm sorry to sound so down, but we have to continually keep up with changes across the entire breadth of the .NET stack, plus Azure (OMG Azure is so huge so fast), JS, HTML, as well as deliver code, pretend we like the latest coding fad, learn an existing codebase, and keep abreast of change in the industry sectors we work in, its very hard work.
Thank you for the video.