Created
August 25, 2016 13:24
-
-
Save jeremydmiller/b4703d3304b6af46e24264611b498fd7 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ASP.Net Core and its MVC framework represent a big change from what's come before from Microsoft. | |
In this talk I'd like to dive deep into the internals of MVC Core to see what lessons we can | |
learn about designing software infrastructure in our own work. In specific, I'd like to dive into | |
MVC Core's usage of middleware, its runtime pipeline, how it supports extensibility scenarios, | |
diagnostics, and application configuration. As an author and maintainer of a | |
common IoC tool (StructureMap), I can speak to the much more complicated way that MVC Core | |
uses IoC containers within its pipeline and the places where I think their usage is going to be | |
problematic for users. | |
As the author of a previous OSS web framework (FubuMVC), I can share some insights by comparing | |
and contrasting MVC Core's solutions to common problems to both the older versions of MVC | |
and some of its existing .Net OSS competitors. | |
While I will have plenty of positive things to say about MVC Core's internals, | |
this talk will also be much more candid, and yes, much more critical than the introductory | |
talks typically given by .Net MVP's. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
just my 0.02, but you might consider changing your verb tenses... from "In this talk I'd like to" and "I can/could" to "In this talk we will dive deep..." Your audience for the abstract is the attendee and you want to make them want to come and listen.