Well, I have to admit it, this comes as a complete surprise for me. One thing is to get Rob Conery into Microsoft (and you, SubSonic was the reason), the other is to privilege SubSonic over LINQ to Entities and LINQ to SQL.
OakLeaf Systems argues:
The problem with LINQ to SQL in a Test-Driven Development (TDD) environment is the difficulty of mocking persistent objects with in-memory objects. That's because there's no memory-based DataContext object you can easily substitute for the DataContext that's bound to the SQL Server 200x instance.
Though in Ian Cooper's opinion:
LINQ to SQL is usable with a TDD/DDD approach to development.
Oh well, not quite the horse I was betting on. And above all, the solution pulverization on this area can turn into trouble. Hope we can get some alternative scaffolding...
No comments:
Post a Comment