Ahh excellent news about the code sharing. The code in the video isn't really readable so this will help alot. I also really like the idea of a ".NET on doverails" project. Thanks again for taking the time to present your work.

*Lies*.

"Unfortunately, we can't find this video! Either it has been deleted, or it never existed in the first place."

Great, thanks for sharing

You've been kicked (a good thing) - Trackback from DotNetKicks.com

I'm interested in how you implement Fluent NHibernate and the Repository pattern.  Can you please include this in your Google Code update? Pretty please? :-)

Pingback from  ASP.NET MVC Archived Blog Posts, Page 1

Pingback from  Dew Drop - November 4, 2008 | Alvin Ashcraft's Morning Dew

Awesome Jeremy! I wish I could have been in Austin to see it and talk about it.  I love the opinionated view of working with Asp.Net MVC.  Its not rails and wasn't designed to be rails... but that doesn't mean you can't easily adopt and create strong conventions that work.

+1 To the recording although it was real tough to see the code.  I can't wait to look at some of the bits that Chad posts.

I used to think alternative view engines were the answer to tag soup... but this clearly shows you can have the strong tool support of asp.net without the soup!

Is there a slide deck available?

Really interested in seeing this, the video you couldn't really see the code and there was a lot of hopping around to show areas of interest.. one area however that I consistently are not 'getting'.. is the view engines.

asp/php they all have this interweaving 'binding' which isn't really binding at all, I find that asp.nets server side controls actually had a good concept that should be rethough for todays expectations..

You may all go nuts, screaming noooo - but I think that xaml has a really tidy binding system.. and I've started to really think recently about how such a 'view engine' could be created.. a xaml inspired binding engine for asp.net, as far as I can tell, this is very much possible with only minimal need for code gen - and wouldn't require any plugs for runtime compilation.. bindings would be captured as expressions that would be evaluated at 'render time'.. you can quite easily cache a resolved markup template and re-use it each time to hydrate data into it.

I'm currently working on this in my spare time, I'm even considering how possible it would be to have extensible input formats, so you could for example write a control or layout in .. json (if you really wanted), and the output would still be the same..

If I get far enough along with this I may codeplex or otherwise to see if there is any interest.. design time support is really the most tricky part.. but as far as I'm concerned.. design time support in asp.net is screwed up anyway.

Pingback from  Elegant Code » Kaizenconf Part 1 - Workshops