oop - How should we use ASP.NET Data Access Classes (Converting from ColdFusion) -

we're converting coldfusion asp.net 4.0 , don't know route take setting our classes.

in college taught break separate data access classes , entity classes speak dac. me, that's best option team needs lot of control on classes , needs reuse multiple items.

then there linq... sure.. it's great , fast! have no problems writing own queries though. me, it's not need. none of on team need linq actually.

i think should using folders contain our daclasses , folders contain our entity classes. have our actual .aspx presentation pages.

any ideas on route should taking?

if you're going go through pain of moving existing platform new 1 anyway, @ asp.net mvc.

the model-view-controller methodology potentially cleaner way of thinking web development, , achieves separation of concerns team seems worried about.

on different note, make sound linq , other such technologies crutches. not unless use them way (as in, not being able data access without it). there tool make life developer easier , development go faster.

knowing how works great, if didn't know of mindset shouldn't use it. state understand it, why not leverage it?