Archive for February, 2008
As I’ve mentioned in other post, while I think LINQ has it’s uses, I still favor the use of the ObjectDataSource control in conjunction with DataSets and a 3-tiered architecture. Since any future demos I do will probably involve this architecture, I thought it would be useful to do a short demo that demonstrates how to create a 3-Tiered architecture in ASP.NET.
Back in December, I did a video about the DotNetNuke event log. A commonly over looked feature in DotNetNuke that can cause your database size to grow for no apparent reason, but also has very valuable information about things that are going wrong in your DotNetNuke installation.
Today, we are going to look at another commonly over looked feature of DotNetNuke and once again, this feature is not only one that can chew up a lot of space if you don’t know about it, it can also save your butt or at least save you a considerable amount of time. Read the rest of this entry »
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?”