I need about MVC Details Following This

Question

hi
1.what is MVC?
2.Why we are use MVC? Advantage and disadvantage
3.Compare 3 tier to MVC
4.why people like this
5.How many Architecture in mvc which is best can u explain them

Note:
Insert,Update,delete using Sql Stored Procedure.

Sam Hobbs · Answer

There are many relevant articles in this web site too.

Senthilkumar · Answer

Hi Jaya Kumar, 1.what is MVC? ). Model: The model object knows about all the data that need to be displayed. It is model who is aware about all the operations that can be applied to transform that object. It only represents the data of an application. The model represents enterprise data and the business rules that govern access to and updates of this data. Model is not aware about the presentation data and how that data will be displayed to the browser. 2). View : The view represents the presentation of the application. The view object refers to the model. It uses the query methods of the model to obtain the contents and renders it. The view is not dependent on the application logic. It remains same if there is any modification in the business logic. In other words, we can say that it is the responsibility of the of the view's to maintain the consistency in its presentation when the model changes. 3). Controller: Whenever the user sends a request for something then it always go through the controller. The controller is responsible for intercepting the requests from view and passes it to the model for the appropriate action. After the action has been taken on the data, the controller is responsible for directing the appropriate view to the user. In GUIs, the views and the controllers often work very closely together. 2) Why we are use MVC? Advantage and disadvantage The main aim of the MVC architecture is to separate the business logic and application data from the presentation data to the user. They are resuable : When the problems recurs, there is no need to invent a new solution, we just have to follow the pattern and adapt it as necessary. They are expressive: By using the MVC design pattern our application becomes more expressive. Advantages: MVC Framework is built upon a proven MVC design-pattern. Hence, this is not a new born baby. One of the biggest problem in ASP.NET is HTML size of controls and view state. View state stores all the data rendered and final HTML gets too large. If you are on a slow internet connection, you will notice load time delays. This has been taken care in MVC framework. There is no view state concept in MVC framework. Client chaching is availalbe now with the help of Silverlight. By integrating Silverlight, we can take advantage of it. That makes applications load faster and some of the processing can be done in web browsers.Not only the client site but the server side execution is faster too. JQuery integration with MVC makes it even better and now we can write our code that runs in the browser and takes away load from the server. Support mutliple views Support unit testing as a part of Visual Studio 2008 and 2010 Disadavantages: Some of the key challanges you may face when using MVC Framework are It is not easy to understand and code when you need some customization. If you are building based on a 100% mature database, they you are golden. But if you have frequent changes in your database, you may find it annoying to keep building application again and again. It may also breake several other parts of your application. If you are using Silverlight part of it, the data access is limited to Web Services/WCF/ADO.NET Data Services. You cannot make direct calls via ADO.NET or stored procedures to a database. Also, you may find it hard to learn LINQ as a new technology to access data. 3) Compare 3-tier to MVC http://www.mvcsharp.org/Overview/Default.aspx 4) Why people like this? 1.reusable 2.expressive 3.easier support for new types of clients 4.it is often seen in web applications 5.synchronised views - Easy to reuse 5.How many Architecture in mvc which is best can u explain them http://www.codeproject.com/Articles/54576/Understanding-ASP-NET-MVC-Model-View-Controller-Ar