Dynamic Data
Akavache
Our great sponsors
| Dynamic Data | Akavache | |
|---|---|---|
| 5 | 3 | |
| 1,665 | 2,414 | |
| 1.4% | 0.5% | |
| 9.0 | 8.1 | |
| 3 days ago | 2 days ago | |
| C# | C# | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Dynamic Data
-
System.Reactive v6.0.0-preview.1 available on NuGet
Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.
-
Property change on multiple objs?
With DynamicData you can use a ObservableCollectionExtended for your list and call .ToObservableChangeSet().WhenAnyPropertyChanged().Subscribe(t => { code to execute });
-
A better way to work with state properties in MVVM
reminds a lot of https://github.com/reactivemarbles/DynamicData
-
Beginner MVVM + Reactive Question (C# + UniRx)
If you're trying to use reactive with MVVM, you might have a look at ReactiveUI, an MVVM toolkit designed to work with reactive extensions. Specifically in this case, you could leverage DynamicData (RXUI's preferred method of handling collections), which lets you trigger updates based on change notification from child items, among other things. I'm still relatively new to RXUI myself, but if you have any questions I can certainly try to help a bit more.
-
LINQ - Selecting from a collection where a collection property contains or does not contain a value
Right and I never said they did. I said replace the observablecollection with an iobservable if you want it to be observable. You can then use https://github.com/reactivemarbles/DynamicData to get yourself an observablecollection. I'm not arguing that observablecollection + linq would result in an observablecollection. Just pointing out that there is a solution for this.
Akavache
-
Storing query results
If its caching you could just use ready made packages - https://github.com/jamesmontemagno/monkey-cache - https://github.com/reactiveui/akavache/
-
How to save the check box state in WPF?
You can check out akavache: https://github.com/reactiveui/Akavache
-
Generate your first Xamarin application with JHipster.NET
akavache >= 7.1.1
What are some alternatives?
Rx.NET - The Reactive Extensions for .NET
CacheManager - CacheManager is an open source caching abstraction layer for .NET written in C#. It supports various cache providers and implements many advanced features.
elsa-core - A .NET workflows library
SqliteCache for ASP.NET Core - An ASP.NET Core IDistributedCache provider backed by SQLite
ObservableComputations - Cross-platform .NET library for computations whose arguments and results are objects that implement INotifyPropertyChanged and INotifyCollectionChanged (ObservableCollection) interfaces.
Electron.NET - :electron: Build cross platform desktop apps with ASP.NET Core (Razor Pages, MVC, Blazor).
ReactiveUI - An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming. ReactiveUI allows you to abstract mutable state away from your user interfaces, express the idea around a feature in one readable place and improve the testability of your application.
Foundatio - Pluggable foundation blocks for building distributed apps.
UniRx - Reactive Extensions for Unity
SharpRepository - C# Generic Repository for use with Entity Framework, RavenDB and more with built-in caching options.
ReactiveProperty - ReactiveProperty provides MVVM and asynchronous support features under Reactive Extensions. Target frameworks are .NET 6+, .NET Framework 4.7.2 and .NET Standard 2.0.
CacheCow - An implementation of HTTP Caching in .NET Core and 4.5.2+ for both the client and the server