Search code examples
c#asp.netvb.netsubsonicdynamic-data

Should I use SubSonic or Dynamic Data for a new CRUD asp.net application?


I need to throw together a quick CRUD asp.net site, but this may become a bigger application down the road. I have some experience with SubSonic, but it has been so long since I did a project with it I have to relearn it. I am also considering using Dynamic Data. Does anyone have any experience with these tools that can tell me which way I should go?


Solution

  • I use subsonic for almost everything these days. The advantage of SubSonic is that you can build whatever abstraction layer you want on top of it, if you need to enhance/extend it later - it really only serves one main purpose - taking the crap out of creating crud code.

    I've not used dynamic data extensively, but from what I've read, it seems like it creates a lot of the scaffolding for you, and it might not mix well with a more extensive application. If you need future extensibility, I'd recommend subsonic, but dynamic data may be the way to go for short one-off applications strictly used to maintain a database via the web.