One of the most common tasks we face as a web developers is displaying data in a grid. In its simplest incarnation, a grid merely
displays information about a set of records - the orders placed by a particular customer, perhaps; however, most grids offer features
like sorting, paging, and filtering to present the data in a more useful and readable manner.
In ASP.NET WebForms the GridView control
offers a quick and easy way to display a set of records in a grid, and offers features like sorting, paging, editing, and deleting
with just a little extra work. On page load, the GridView automatically renders as an HTML
element, freeing you from having to
write any markup and letting you focus instead on retrieving and binding the data to display to the GridView. In an ASP.NET MVC application, however, developers are on the hook for generating the
markup rendered by each view. This task can be a bit daunting for developers new to ASP.NET MVC, especially those who have a
background in WebForms.
This is the first in a series of articles that explore how to display grids in an ASP.NET MVC application. This installment starts
with a walk through of creating the ASP.NET MVC application and data access code used throughout this series. Next, it shows how to
display a set of records in a simple grid. Future installments examine how to create richer grids that include sorting, paging,
see how to display database records in a web page.
Complex hybrid environments can make it difficult to track interdependencies, increasing the risk of disrupting critical business services. In this white paper by EMA, you'll learn how application discovery and dependency mapping can help you:
Meet granular targets for availability, cost, and time-to-revenue for cloud services.
Accelerate mean time to repair (MTTR) while communicating better with stakeholders.
Manage even the most complex hybrid environments more efficiently and effectively
Understand the …
Following an IT incident through to resolution is more than just acknowledging an alert and restarting a server. The recent State of On-Call Report found that it takes most companies an average of 10-30 minutes to resolve an incident with an average of 5 people involved. Imagine how much money and time companies are spending to deal with incident resolution.
But what if you had a tool that offered solutions baked in? Or a tool that sent alerts to the right person or team every time? These are the kind of …