>Is there any benefit to converting my data access layer to Linq To SQL?
I should have provided more background.
I'm well into learning WPF and the MVVM model, and I'v seen many examples that show the models populated using Linq to SQL.
These model classes, in most cases, are just collections of properties that represent an entity in the DB. Pretty typical. So to me,
how you go about getting the data to populate the model is sort of irrelevant.
My DAL layer allows for either T-SQL or SPROCS, and I'v had no real problem with it. I know next to nothing about Linq. I want and
need to learn Linq more, but my question stems from my observation that alot of these models are populated using Linq. But before
I throw out perfectly working code, I need justification.
FWIW, I like SQL and have no issues using stored procs. I have listened to the arguments for & against SQL over the years and
don't see what the fuss is all about.
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people