Posts Tagged ‘linq’
One thing I didn’t get around to mentioning the other day when I was evaluating if LINQ 2 SQL with the LinqDataSource really is multi-layered or not is my belief that what Microsoft has really (re)created for us is the Document/View architecture all over again.
That post was an evaluation. This post is a rant. The two have no place together.
Several weeks ago, we discussed the point of Multi-Layered Architectures. We discussed what a multi-layered architecture looks like, and the problems it solves.
Today, what I want to examine is the question, “Is the LINQ model we’ve been looking at since then really multi-layered?”
While it is true that LINQ will allow you to write all of your data access in .NET without writing a line of SQL, many organizations have already determined that using stored procedures to retrieve the data from their database is the preferred way of accessing the data.
As promised a few days ago, I will be covering multi-layered architecture as it relates to LINQ.
The first thing we need to evaluate is how Microsoft intended multi-layered architecture to work. I mean, if we want to know how to do this, the best place to start is with the people who created the technology in the first place, right?