As far as more work, I am not sure I agree with that. I think this is less work than even say nhibernate. There are no mappings to create. There is not database schema to create or push to the different environments. Those things are getting easier to manage, but they take time to get in place and I would personally like to delay that work until after I am demonstrating value in the project. Either way I should be working through these issues in the next few posts and we will see what comes of this crazy idea.

Although, This seems like a lot of extra work for prototyping.

I personally just use a generic repository with nhibernate, supplying an alternate config for a sqlce database on test runs. A throw away database if you will. This way all I have to do is create the repository implementation to go to production.

Do you use this a lot or are you testing it out? I would like to know how it works in a real world situation. If it’s not too difficult I would consider giving it a shot myself.