Business Objects

[Nate Bross]

Is it a bad idea to use expose LINQ to SQL objects as data objects?

 

It exposes the presentation layer directly to the database, even if it is through a class, that class directly relates to the database fields, etc which is supposed to be bad, right?

 

If that is the case, then what use is LINQ to SQL doing the busy work of creating my business object classes for me?

 

Thoughts?

[PlausiblyDamp]

I personally don't have too much of a problem with this - it makes your life easier as you do not have to create the object model yourself.

 

If the database is still fairly changeable though then you could encounter a lot of problems as schemas change and the Linq to Sql model needs to be kept in sync.

 

 

For anything more complex I would probably look at a more mature O/R mapper as this kind of problem is often addresses by the O/R mapper itself.