c# - In what order should we implement Asp.Net Mvc App -


This may be strange question but I just started a new medium size web application using an SP.NET MVC I am goig for it.

Every person has his attitude towards solution, but always some practices are followed.

  • BLO (Business Logic Layer + Business Objects)
  • Front End (
  • Authentication, Testing (Integration) and Other etc

( Parallel unit test starts with BLL)

Now I have completed MVC books and tutorials and work on application The database is already in. I am using LinqToSql for the Dal (model).

Models , View And Controller . I am confused because all the tutorials have different perspectives.

As with some routing starts with the table, some start with the controller component , Then touch the scene, then suggest logic to make changes to the model, "if the controllers While growing, ".

Some of the administrators teach to work on the set -> refer to each process in the specification (s) -> model (model).

I'm not sure what the right approach is. It would be nice to have words above the order used to implement your components / steps. I'm not sure about the phase that the unit will start testing for.

I have tried to clarify myself, please ask whether or not you welcome the title or post edit, if you think that would be better.

Note: will use C #, SQL Server 2005, JQuery, CSS, Visual Studio 2008 and a team of two, beta versions and many other revisions (components) expected. Thanks

I start with the user interface and work backwards. This is because I can work with users and business analysts because I create an application. I have underlined the general process


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -