Hello All … many of us have heard of ASP.NET as a web development technology. But many of us does not noticed that things differs a lot from ASP.NET 1.1 time.
So what is the difference?
Since ASP.NET 2.0-3.5 has been released we have multiple flavors of ASP.NET. This means that you can develop ASP.NET web application using different asp.net frameworks. You may select the framework you think its the most efficient to your situation. That is really great thing to have because its provide developers with sufficient flexibility needed to let there job done.
ASP.NET Flavors
Since there is much of articles, posts about ASP.NET new era I will just summarize them from Paul Litwin blog post in which he talked about this pillars in details. Thanks Paul.
ASP.NET Web Forms
Until recently, this was the only pillar of ASP.NET. Everything was done using the familiar rich server-side controls that many have grown to love (and some have learned to despise which is the seed for the other three pillars). Event Driven development model, very powerful designer support, and persistence in mind.
This pillar came to life with the ASP.NET AJAX Extensions for ASP.NET 2.0 / Visual Studio 2005. ASP.NET AJAX is now integrated into ASP.NET and Visual Studio 2008 and consists of both a set of server-side controls as well as the AJAX client-side libraries. In regards to its existence as a “pillar,” I would argue that Microsoft is really only talking about the client-side of ASP.NET AJAX. The reason I say this is that the Upgrade Panel and other server-side AJAX controls merely extend the Web Form pillar, giving Web Form controls the ability to do asynchronous postbacks.
This pillar is the newest to emerge from Microsoft. In fact, as of this writing, it’s only a couple of weeks old, having been released at Mix09. The basic idea behind ASP.NET MVC is to separate out the three concerns of the MVC pattern: the model, view, and controller. The model represents the data model, the view is the user interface that presents the data and interacts with the user, and the controller is the command center that takes inputs from the view, pushes and pulls data into/from the model, and decides what to do next.
MSDN Help says, “ASP.NET Dynamic Data is a framework that lets you create data-driven ASP.NET Web applications easily.”
Dynamic Data uses what is termed dynamic scaffolding to construct your application. This means if you change your data model, the application will be instantly updated: there’s no code that needs to be re-generated.
So what does this mean to the developer?
As Paul said this is good news as that you now have a choice in how you develop your ASP.NET applications. And its bad news as that you now have a choice in how you develop your ASP.NET applications. (Wait a second, wasn’t that also the good news?)This means you have more things to learn. And Microsoft may be taking some of its focus off Web Forms.
For more details you can refer to Paul’s nice post and have a extensive idea bout those options and comparison between them. Regarding myself I still stuck with ASP.NET web forms which I feel its more appropriate and easy to use.
Hope that helps
Huhaifa