May 08, 2009 07:12 PM|BrianPritchard|LINK
I'm trying to design from a domain/model driven approach.
I'm not modifying any generated code, I'm mapping the model to the database myself with [Column] attributes. You don't have to use the O/R designer to use linq to sql you know.
So why would wanting to make something private be the wrong approach? It's basic OO to only expose what you really have to. Dynamic data may not be the only client of my model.
If DD needs public foreign key fields to navigate, I guess I can live with that, but I don't think its wrong to want your model expressed in terms of objects instead of keys.
Still, I don't want everything that is persisted by linq to sql to have to be public. I don't see why this wouldn't already be supported. Why can't it just ignore anything non-public?
Anyone know of a way arround this?