ASP.NET MVC Application In Action - I (DailyJournal)

Posted by Rajesh Pillai on Geeks with Blogs See other posts from Geeks with Blogs or by Rajesh Pillai
Published on Fri, 21 May 2010 01:57:44 GMT Indexed on 2010/05/21 2:40 UTC
Read the original article Hit count: 370

Filed under:

Its been long due I was planning to write an article on creating some useful ASP.NET MVC application. I have code named it "DailyJournal". Its a simple application which allows creation of multiple activities and assign tasks to these activities. Its' kind of "Yet another Task/Todo application".

The credentials which you can use with the attached demo application is shown below.

 

Collapse Copy Code
User Name : admin 
Password   : admin123

Framework/Libraries Used

  • ASP.NET MVC
  • jQuery + jQuery UI (for ajax and UI)
  • ELMAH for Error logging

Warning Ahead

This is just a rough draft and so I am putting down some of the known limitation.
Some points of warning before we move further with this application. This is just an early prototype. As such many of the design principles have been ignored. But, I try to cover that up in the next update once I get my head around this.

The application in its current state supports the following features

  • Create users
  • Assign Activities to users
  • Assign tasks to activities
  • Assign a status to a task

The user creation/authentication is being done by the default Membership provider. Most of the activities are highly visual i.e. you can drag-drop task to different areas, in-place edition of task details and so on.

 

The following are the current issues with the design which I promise to refactor in the second version.

  • No Validations
  • Fat Controller
  • XSS/CSS vulnerable
  • No Service model/abstraction yet. For the demo LINQ to SQL is implemented.
  • No separation of layers
  • UI Design
  • et el...

This is just an extract.  For source code and more information proceed to

http://www.codeproject.com/KB/aspnet/mvcinaction.aspx

Hope you like this!

© Geeks with Blogs or respective owner