> I've just had a quick look at Massive and Dapper.. Both appear to use the > MS.Net 4.0 System.Dynamic namespace to do their "dirty" work.. Looks > powerful.. MSDN Mag had an article on this not so long ago, was a good read > and looks very powerful. > > Massive looks like it's basically attaching the DAL layer to every entity. > Is this assumption correct ?? > What's people opinion on doing this ?? > It seams to go against the theory of n-tier dev if the db connection is > within the entity object. Is this what people are doing ?
I don't like it; but I also don't like the dynamic concept or the new direction of .net in general, so it shouldn't be a surprise. But also, I don't particularly see a compelling reason to use Dapper over what I currently use (LLBLGen). But I've not actually tried it for myself, so it's possible that it offers something compelling. I can't see it, from the website, though. -- Noon Silk http://dnoondt.wordpress.com/ (Noon Silk) | http://www.mirios.com.au:8081 > Fancy a quantum lunch? http://www.mirios.com.au:8081/index.php?title=Quantum_Lunch "Every morning when I wake up, I experience an exquisite joy — the joy of being this signature."
