"Why data virtualization? Say, you want to display a table from a database which contains thousands of rows in your WPF-application. If an ordinary list is used in combination of a DataGrid, then all the rows have to be loaded into memory. Even though, the amount of rows which can be displayed at once usually doesn't surpass 50 rows. Fortunately, DataGrids have UI-virtualization integrated. Which means that only the visible rows get representing UI-elements. However, still the whole data has to be loaded into memory. In order to virtualize the data in analogous manner to the UI-elements data virtualization has to be used. How? Data virtualizing collections act as if they have all the data. However, they only fetch the data wich is currently requested on demand. Usually the data is fetched in chunks called "pages" of fixed size. For example, if the page size is set 100 and the DataGrid is initially pointing to the top most row with index zero, then initially only the first 100 elements (i.e. the first page) is fetched. As soon as the user scrolls further down and the row with index 100 is displayed, another page is loaded. The advantage is generally a better performance and less UI freeze, because lesser data is loaded at once and only on demand. Furthermore, the memory consumption improves as well. Use case of this project Up until now this data-virtualizing collection has been used exclusively for WPF-DataGrids. Hence, it wasn't tested for other ItemsControls. However, it is assumed that they work similarly to the DataGrids. The ItemsSource of DataGrids accepts arbitrary instances of IEnumerable. Which would be problematic from data-virtualizing perspective. Fortunately, the DataGrid are optimized to IList implementations and use theis indexers if the ItemsSource is castable to IList. This project uses it to its advantage in order to track which indexes were requested in recent past. Therefore, only page can be loaded only on demand. For further information please refer to the github page of this project."
Project website: https://github.com/Yeah69/BFF.DataVirtualizingCollection
"YamlDotNet is a .NET library for YAML. YamlDotNet provides low-level parsing and emitting of YAML as well as a high-level object model similar to XmlDocument. A serializ…"
"XamlCSS lets you style XAML applications with CSS. It combines the lean syntax and the the hierarchy-based styling of CSS with the native styling systems of the 3 major …"
"Cofoundry is an open source .NET Core CMS designed to work unobtrusively with your application. It's simple to install and our code-first approach to content and feat…"
"AspNetCoreRateLimit is an ASP.NET Core rate-limiting solution designed to control the rate of requests that clients can make to a Web API or MVC app based on IP address …"
"An SDK for Sentry which is an OSS error tracking tool. The SDK is to be compatible with most .NET apps so the unit and integration tests run on .NET Framework, Mono and …"
"Think Laravel meets .Net Core. In app task scheduling, queuing, caching and (coming soon) mailing and CLI! Coravel wants you to starting building your app, instead of wa…"
Hello, I'm Corstiaan. I'm a .net developer from the Netherlands and I manage BuiltWithDot.Net. I created this site as a place where developers working with .net technology can showcase their projects and inspire other developers.
There's so much you can build with .net these days that I thought it would be nice to have a corner of the web dedicated to the breadth of .net. Enjoy!
Get weekly updates about new projects built with .net tech
No spam. Unsubscribe any time.