aspConf 2012 Sessions

Yesterday I presented two sessions for aspConf 2012. The first was a new talk I haven’t given before on ASP.NET MVC Solution Best Practices (which I dubbed the Solution to the Solution Problem). The second one was a talk on Common ASP.NET Design Patterns, which is basically I talk I’ve given for at least a year now on Common Design Patterns, adapted slightly for ASP.NET (mainly MVC). The slides are shown below. The sample code for the MVC Solutions talk used a simple Guestbook application found here. The samples code used in the Design Patterns talk is a fork of the MVCMusicStore application found here.

ASP.NET MVC Solution Best Practices

Common ASP.NET Design Patterns

Video of the presentations is supposed to go up on Channel 9 at some point – I’ll update this post once that happens.

  • Mubeen Jassani

    Enjoyed both the talks… It’s always a pleasure listening to you!!!

  • George

    Great talk. Enjoyed your presentation on Design Patterns.

  • Jesse Williamson

    Woohoo! Teh codez!!!!!!!!

  • Doug

    Looking forward to the videos. Please don’t just update this post though as I’ll never see it… A new post will show up in my feed reader.

  • bjorn

    Thanks for great talks on aspConf. Can’t find the videos on channel9. Do you know if they will be there?

  • Glen

    The videos are coming.  Volunteers are working through the editing of the 60 videos from aspconf.  I can say for sure the common design patterns video was just finished 2 minutes ago.  Hopefully it’ll make it up on channel 9 in the next couple days.

  • bjorn

    That’s excellent! Thanks

  • Jeff

    The ASP.NET MVC Solution Best Practices video has been posted

  • Ken Nagorski

    So what was the other tool besides n depend? 

  • Steve Smith

     Nitriq, probably.  Jon von Gillern wrote it; NimblePros used to sell it.  The site’s down apparently at the moment, but the twitter is here:

  • Steve Smith

    Both are now online – find them here:

  • Greg

    This was a great video! Really helped me wrap my head around these concepts. I do have 1 question.

    You mentioned in the video that the Infrastructure shouldn’t be referenced in the Controller but finished your presentation. Just curious.. Should I be using the WEB API to communicate between the “CORE” project and UI… I’m kind of stuck on deciding what technology to use that will keep the UI decoupled from the CORE libraries ..
    In my eyes it should be Infrastructure < – > Core <– > WEB API? <-> UI..

  • Steve Smith

    Hi Greg

    The Controller should only know about the abstractions it depends on, the interfaces defined in Core. The IOC container can inject the actual implementation (from Infrastructure) at runtime. You can see an example of this in action in my Pluralsight course:

    Web API is not the answer. You can think of Web API as a separate UI layer. Your Web API services, if you have them, should not know anything about their implementation any more than your controller actions should. Generally, the Web API classes are going to be called from your front end (browser or [mobile] app), almost certainly not directly from a controller.