Building a Simple Blog Engine with ASP.NET MVC and LINQ

Print Add To Favorites Email To Friend Rate This Article
Building a Simple Blog Engine with ASP.NET MVC and LINQ - Part 1

page 1 of 8

Published: 21 Jan 2008

Abstract
Microsoft released the first CTP of ASP.NET 3.5 Extensions and it includes ASP.NET MVC Framework as one of the main extensions for ASP.NET 3.5. In the first part of this article series about building a simple blog engine with ASP.NET MVC and LINQ, Keyvan introduces the MVC pattern, ASP.NET MVC Framework, and the fundamentals of a simple blogging engine.

by Keyvan Nayyeri
Feedback

Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 26143/ 401

Article Contents:

Introduction

A few weeks ago Microsoft released the first CTP of ASP.NET 3.5 Extensions which includes the first public version of ASP.NET MVC Framework. There have been many good resources about this MVC Framework on the web as tutorials, blog posts and web casts.

I want to write a set of articles about ASP.NET MVC Framework to build a simple blogging engine based on MVC and LINQ in .NET 3.5 and show you all the steps in detail then extend the discussion to some more-in-depth topics. I have not written this application completely and will write it in parallel with these articles.

Such a sample application is provided by ASP.NET MVC toolkit, but there is not a description about it yet. But why I am doing this while there are some other tutorials with the same approach? In my opinion, the learning curve of this MVC Framework consists of a workflow progress of some steps that should be followed and the major thing is this, building this simple blogging engine and describing its process would be a very good example for ASP.NET MVC Framework.

So here is the first part of this series (I want to finish them in a few weeks) and it is an introduction with some basic information.

View Entire Article

(Page 2) »

Article Feedback

Comment:
Title:
Name:
Url:	( Optional )

Please add 8 and 3 and type the answer here:

User Comments

Title: about blog
Name: rem
Date: 11/16/2008 3:41:24 AM
Comment:
nice blog...

Title: about post
Name: Rem
Date: 11/4/2008 6:10:36 AM
Comment:
Nice post...

Title: BlogService open source blog engine on MVC
Name: Jarrett
Date: 10/18/2008 5:48:48 PM
Comment:
There is an open source blog engine called BlogSvc over at

http://codeplex.com/blogsvc

Check out the source code.

Title: How...
Name: AmyJK
Date: 6/5/2008 6:27:20 AM
Comment:
How do i get hold of the extentions?

Title: Part 4
Name: Keyvan Nayyeri
Date: 5/2/2008 3:01:15 AM
Comment:
You can read the fourth part here:
http://aspalliance.com/1630_Building_a_Simple_Blog_Engine_with_ASPNET_MVC_and_LINQ__Part_4

Title: Part 3
Name: Keyvan Nayyeri
Date: 3/5/2008 1:35:04 PM
Comment:
You can read the second part here:
http://aspalliance.com/1604_Building_a_Simple_Blog_Engine_with_ASPNET_MVC_and_LINQ__Part_3

Title: Part 2
Name: Keyvan Nayyeri
Date: 3/5/2008 1:34:21 PM
Comment:
You can read the second part here:
http://aspalliance.com/1559_Building_a_Simple_Blog_Engine_with_ASPNET_MVC_and_LINQ__Part_2

Title: Download
Name: Alexandre
Date: 3/3/2008 3:09:17 PM
Comment:
How may i download it?

[]s

Title: Great starter kit
Name: dotservant.com website hosting services
Date: 2/21/2008 3:26:26 AM
Comment:
Great introduction to MVC and a simple hands on exercise for a quick run through of the general concept of ASP.NET MVC.

Title: Comment on Figure 1
Name: Keyvan Nayyeri
Date: 2/4/2008 12:59:35 PM
Comment:
Dave,

Thank you for leaving your comment. If I can remember it correctly, I took Figure 1 from MSDN. Yes, there can be a two-way connection between controller and view but don't forget that this isn't mandatory. There may be some cases where controller gets data from view to perform an update but this isn't 100% a case for all scnearios.

I hope this makes sense.

Title: Figure 1 (MVC structure) is incorrect
Name: Dave
Date: 2/4/2008 12:40:04 PM
Comment:
The view NEVER(!) updates the model. The controller is responsible for loading and saving states to the model layer. Loaded information from the models layer is than passed the the view. The view does only presentation. By definition it is impossible that a presentation contacts the models view or even updates it. The controller is responsible for all logic needed to view, create, update or delete a page.

(I hope my schema stays correct)
+------------+ +-------+
| controller | --- loading information --> | model |
| | <-- saving information ---- | |
+------------+ +-------+
|
V
+------------+
| view |
+------------+

(Basicly your have to define a two-way (loading and saving) connection from the controller to the model. The controller has a 'write-only' connection with the view.

The rest of the article is written very well. Keep up the good work!

Title: Great
Name: Santosh
Date: 1/29/2008 1:16:45 PM
Comment:
Nice article, easy to undestand!

Title: Nice
Name: Gustavo
Date: 1/24/2008 1:45:58 PM
Comment:
Keep Going...
I want to see the final result soon! =]