Let's take a look at our solution.
Let's start our solution by first discussing the implementation of our database.
As we discussed before, the concept of a category is our top level container of data. Let's take a look at the table structure for categories:
The SortOrder field is in charge of setting the display order in case we have multiple categories on one page. We already discussed the count fields earlier. The last X fields are to control who made the last post and when. PageName controls the friendly URLs that our system will use later.
Note
Some of you may notice that the name of this table is BoardCategorys instead of BoardCategories. I have noticed that while dragging some spellings into the LINQ to SQL designer I get odd spellings for my object names. Where I could go in and rename the objects for each table I find that it is easier to just work with the issue in a way that LINQ to SQL will generate what I want in the first place. This...