Actions are public methods in controller classes. MVC provides attributes to tweak how the actions can be selected based on the name or the request verbs.
UpdatePanel encapsulates almost everything about AJAX. In some cases, it is good thing. But in some other cases, it is pretty restrictive. ASP.NET AJAX provides a way to handle AJAX lifecycle from the client side. It is the best part of the library IMHO.
The “GridView” control is very versitile. Displaying data in a grid is one thing. You can perform actions per row such as editing and deleting. Also, you can provide a select button that can be used for master-details views.
The “GridView” control has a built-in support of sorting and pagaing. They are very powerful features but needs to be used cautiously.
“Repeater” is the simplest composite data-bound control. It has no built-in layout or styles and does not provide selection or editing features. Also, by default it doesn’t provide paging and sorting of items.
Repeater has been used since .NET 1 so there are a lot of legacy code that uses Repeater controls. Since .NET 3.5, it is recommended to use “ListView” rather than “Repeater“.
Links are created by an anchor tag “<a>”. In ASP.NET forms, the “HyperLink” control is used to create a link. But you can navigate to other pages through other ways such buttons or clickable areas.
By providing event handlers to “AjaxOptions“, you can control each step of Ajax request and response.
So far, we have used Unobtrusive Ajax with a form and a submit button. What if you want a link that acts asynchronously?