I've really appreciated these videos.  Thank you.  But at some point the videos stopped and the downloaded code changed completely.  When I first began watching, I thought the purpose of the videos was to demonstrate how to use MVC to create a storefront application while using best practices.  As things progressed, so many things were discarded that a large number of earlier videos no longer apply.   Shouldn't the best tools and best practices be known before the application starts.  Yes I realize software is an iterative process. But the huge changes in architecture aren't very practical and are disastrous when creating actual applications under time constraints.

Hi Geomar - Best Practices shift a lot and are different things to different people. For instance - if you ask some of the Alt.NET folks what Best Practices are you'll get a completely different answer than someone who has just as much experience but doesn't adhere to the things they do.

My goal with this series was exploration, not telling people what to do, so you could make up your own mind :).

Finally - the current codebase is explained here: http://blog.wekeroad.com/kona/kona-1/

The idea is that this app needs to be highly flexible and extensible so we're changing things up. I'd like to ask you to be more specific about things not being practical and "disastrous". How so?

Thanks Rob.

I am in the process of learning MVC. And in addition to the Store Front, I am working my way through the Videos and Tutorials on the ASP.NET MVC site.   As you know, these sources also utilize other tools like Linq To SQL, Entity Framework, and in the case of the StoreFront, StructureMap. Fantastic.

One of the many things I liked about StoreFront is that the architecture broke the MVC application into multiple tiers.  The tiered approach seems more realistic for real life applications, while the single tier was practical for a tutorial.

My expectation was to discover the best practices for enterprise level MVC.  The earlier videos mentioned that the application was being prepared for an "Imaginary Client".  I assumed this meant a more structured instead of exploratory approach.  When I used the words "disastrous", I did not mean the StoreFront project.  I meant that if I was architecting an application for a real client, on a time schedule, it would be "disastrous" for me to continually change the basic architecture of that application.

As with any software application, there are many choices and options. Within those choices though, I think there must exist something called best practices.  There doesn't seem to be a lot of time or tolerance to experiment with new technologies on the client's dime.  So I suppose you could say I was looking for ways to learn as quickly as possible.

I'll check out Kona.  I appreciate your time and hard work.

Thanks again