Comments

Yep, exactly. Unfortunately, because we're trying to be cutting edge with this show, stuff WILL change between an episode being published and new versions of the bits coming out

Yep, you'll need to include the JavaScript files. Just keep in mind that the ScriptManager control in ASP.NET WebForms was the one that was including the ASP.NET AJAX libraries for you, so once you aren't using it, you'll have to include the scripts manually.

AjaxRes.js is actually an artifact of the internal builds that I was using for the video If you grab the latest bits off of Codeplex, you won't need it.

Sounds like what you want it to use Dynamics as your data store/platform, and then place the Entity Framework over it so that you can program against its dynamic entities. If so, the guys over at ADX Studio (http://www.adxstudio.com/) are working on something that handles this very nicely.

I'll definitely be digging into the code much more moving forward. This episode was just an initial introduction to the high level changes coming. I'll make sure to provide plenty of good detail/usage examples

Thanks for the heads up bertnz. The ORM space certainly has lots of great options.

LINQ To SQL is getting quit a few improvements in the .NET 4 timeframe. You can see a pretty comprehensive list here: http://damieng.com/blog/2009/06/01/linq-to-sql-changes-in-net-40

As far as the Entity Framework being the preferred option for data access moving forward, yes, that is the case.

haha very well played

I would go with the unique string approach. Since part of the whole objective is to provide more meaningful URLs to end users, integer/guid identifiers don't really provide them any value. That doesn't mean that you won't still need to do something along the lines of "Products/1" in situations were that makes sense. You might have resources that don't legitimately have a unique value other than an ID. For SEO purposes having a descriptive value in the URL certainly helps as well. "Products/Cups" is capable of being spidered as a resource on "cups" whereas "Products/45" isn't. Will that make a huge difference? Maybe not, but every little bit helps

There is no need to get religious on either approach, it all just comes down to which approach serves the needs of your application the best. Since routing is so extensible, you should have fun building the sitemap you want. There is soooo much more to it then what I showed in this demo since this episode was meant only to show how routing and webforms can work together. General purpose routing has plenty of awesome little features.

I doubt there will be a 10-4 episode on ASP.NET Routing specifically since it isn't a feature in .NET Framework 4.0, but I could throw together some ad-hoc screencasts and plop them on my blog (http://www.lostintangent.com) or C9.

Keep these great questions coming guys, I seriously love the 10-4 community

That is one of the first questions that always comes up after seeing ASP.NET Routing As of right now the only way to configure your routes is through code. That said, I'm a firm believer that a good API is the perfect foundation for layering additional forms of expression (i.e. loading routes from a config file or DB). There are a couple prototypes floating around that pull your route definitions from config that I'd be more than happy to share with you.

As far as new rendering of controls, I'll deifnitely try to fit this in later episodes. Funny enough I actually showed off a very subtle change to the ListView control in this episode but I didn't call it out. You no longer have to have a PlaceHolderTemplate if your ItemTemplate's contents are truly seperate markup (i.e. not <li>'s within a <ul> for instance).

Feel free to email me (joncart at microsoft dot com) and I can share some additional info in the meantine.