So far in my applications, I have been using the Entity Framework for object persistence (why? SQLite is why).  Unfortunately, I also like to write lots of unit tests.  Normally, this would be a problem, as the entity container would be coupled to the controllers.

Just a quick post for something I only today noticed in the Visual Studio 2010 beta – and its damned cool.

I apologise in advance if this post seems slightly incoherent - I write this whilst on a train, and its quite a bumpy ride.  Also, another disclaimer - the code you're about to see will be soon heavily refactored and improved; don't expect it in this state to be amazing!  For one, truncating the post content will be moved to the model level, and the post mark-up will be moved to a user control.

Not long ago I had no idea what the point of ASP.NET Dynamic Data was.  I simply could not 'grok' it, until very recently when I tried using it for a client's CMS.

Nice to see that finally ASP.NET MVC has been released!  Been using it since the very first preview, and it's been a blast.

One thing that has certainly sped up my development time is using ADO.NET Data Services with my AJAX.  Instead of having to build controller actions or a web service to grab the data, i can just consume it from the data service directly.

Been playing around with ADO.NET Data Services this morning - really cool how you can point it at your (Entity Framework in this case) data model, and it fully exposes it via a web service.