List View is a data bound control similar to Data List and Data Repeater controls but it provides edit, insert, and delete , sort operations on the data that it bounded like a Grid View control.
Unlike Grid View control List View gives the user full control over the rendering of the page.
Using these controls can provide development efficiency when you are building business applications that rely heavily on data. A data source can be a relational database, data stored inside of in-memory objects (such as a Data Set or an Entity Data Model), XML-based data, or data you retrieve via Microsoft Language-Integrated Query (LINQ).
The second lesson in this chapter demonstrates how you can bind to data to allow users to interact with it.
This sample is using Access Data Source control to bind to the List View control.
List View provides built in support for sort functionality.
List View implements the IPageable Item Container and will use Data Pager to support Paging.
In this tutorial we will use both the controls to achieve an email Viewer look and feel like below image. NET datasource control to bind to the List View control by setting the Data Source ID property of the List View control to the name of the Datasource control.
They make it easier to build webpages that access, display, manipulate, and save data. You use these controls to configure access to data that you intend to use on a webpage.In addition, you should be comfortable with all of the following: REAL WORLD: Mike Snell Not all applications require developers to write custom, abstracted data layers and reusable frameworks.I’ve seen many simple business applications that suffered from over-engineering. NET can now generate a data layer for you by using LINQ to Entities.Many of these smaller applications can take advantage of the simple data-binding techniques built into the Visual Studio ASP. These applications can be created quickly, typically do not require much testing, and allow developers to focus on solving business problems rather than building frameworks and reusable objects that might never realize the goal of reusability. Applications that can benefit from this approach often have a common profile: they typically have compressed schedules, are meant to be websites from beginning to end, and might fill a somewhat temporary need.
When optimizing for these considerations, you might find that building data-bound applications by using the server controls in ASP. Data source components offer an alternative to the classic ASP.