Hi everyone.
I’m confused about the custom sorting mechanism for the Article Comments in TBH. We have to display the comments on the ShowArticlePage in the chronological order without pagination. For this we can use “tbh_Article_GetCommentsByArticle” stored procedure. On the admin page, ManageComments, we have to display all the comments from newest to oldest with pagination support. For this we can use “tbh_Article_GetComments” stored procedure. Since we have two different SPs for these two pages, why don’t we just sort the results of “tbh_Article_GetCommentsByArticle“ SP from oldest to newest without pagination parameters and the results of “tbh_Article_GetComments” SP from newest to oldest with pagination parameters ? Why we need custom sorting mechanism in the Comment class?

I agree with you -- for the functionality developed in the book, the CommentComparer class is not really necessary, as we are using the methods in question in only two places, and there is no need to reverse the order if you sort it they way you want directly in the SP. You'll also notice that CommentComparer allows for sorting by AddedBy as well as AddedDate, and that functionality is never used either.

I actually should say three places, as GetComments is also used in the Article class to define the Article.Comments property. However, I don't see a definite need to sort in descending order for that.

It is a good demonstration of how to implement IComparer though.

yep, I was thinking the same thing, its a good demonstration to implement IComparer, but I was wondering it didn't seem neccessary. Atleast I'm happy I wasn't missing anything.. thanks for your confirmation..!