This might be odd question but I am just goig to start a new Medium size WebApplication using Asp.Net MVC.
Every person has his own approach towards a solution, but there are always some practices followed.
While Working With Asp.Net Forms Application I always, worked in following order
- Database
- Data Access Layer (LinqToSql / Ado.Net Entities etc)
- BLL(Business Logic Layer + Business Objects)
- Front End ( Forms, design etc and)
- Authentication, Testing (integration) and others etc
(parallel unit testing starts with BLL)
Now I have finished MVC books and tutorial and about to start working on Application.
Database is the already there. I will be using LinqToSql for DAL (Model(s)).
What Order Should I follow for the implementation of Model, View and Controller. I am confused as all tutorials have different approach.
Like. some start from routing table, some start from Controllers Component, then touch Views, then advise to shift the logic into models, “If Controllerskeep on growing”.
Some Teach to work on Sets of Controller –> View(s) –> Model(s), for every process in the specification.
I am not sure what is the right approach. It would be great to have word over the order you use to implement your components / stages. I am also not sure about stage for starting unit testing.
I have tried to make myself clear, please do ask if not sure, You are welcome to edit title or the post itself, if you feel that would be better.
NOTE: will use C#, Sql Server 2005, JQuery, CSS, Visual Studio 2008 and a team of two, beta version and expected several revisions (components).
Thanks
I tend to start with the user interface and work backwards. This is so that I can work with users and business analysts as I build up the application. I have outlined the general process in this post.