Chinook.DataLoader.Uno 1.2.0

There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package Chinook.DataLoader.Uno --version 1.2.0                
NuGet\Install-Package Chinook.DataLoader.Uno -Version 1.2.0                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Chinook.DataLoader.Uno" Version="1.2.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Chinook.DataLoader.Uno --version 1.2.0                
#r "nuget: Chinook.DataLoader.Uno, 1.2.0"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Chinook.DataLoader.Uno as a Cake Addin
#addin nuget:?package=Chinook.DataLoader.Uno&version=1.2.0

// Install Chinook.DataLoader.Uno as a Cake Tool
#tool nuget:?package=Chinook.DataLoader.Uno&version=1.2.0                


License Version Downloads

Customizable async data loading recipes for MVVM development.


🎥 Here we can see the loading, error, and data visual states.


  • Highly Extensible
    • Everything is interface-based to easily allow more implementations.
    • A single framework can't cover everything. Our architecture is designed in a way that allows you to integrate your favorites tools easily.
  • Highly Flexible
    • "Data loading" is a broad topic. We aim for our recipes to be flexible enough to support as many use-cases as possible.

More like this

The Chinook namespace has other recipes for .Net MVVM applications.

Getting Started

  1. Install the latest version of Chinook.DataLoader.Uno or Chinook.DataLoader.Uno.WinUI in your project.

  2. Add a IDataLoader to your ViewModel.

    public MainPageViewModel()
      MyAsyncValue = DataLoaderBuilder<int>
    public IDataLoader<int> MyAsyncValue { get; }
    private async Task<int> LoadMyAsyncValue(CancellationToken ct, IDataLoaderRequest request)
       // Your async operation here.
       await Task.Delay(1000, ct);
       return default(int);

    💡 If you use Chinook.DynamicMvvm, you can simplify the declaration. More on that here.

  3. Add a DataLoaderView style in your xaml. <details> <summary>Expand to see code sample.</summary> <p>

    You can add the following DataTemplates and Style to you Page.Resources or to a merged dictionary in you App.xaml. Feel free to copy and modify this code.

    <DataTemplate x:Key="DataLoaderViewEmptyTemplate">
             <TextBlock Text="Nothing to show here"
                         Margin="0,44,0,0" />
     <DataTemplate x:Key="DataLoaderViewErrorNotificationTemplate">
         <Grid Background="#570000"
                 <ColumnDefinition Width="*" />
                 <ColumnDefinition Width="Auto" />
             <TextBlock Foreground="White"
     <Run Text="Something went wrong." />
     <Run Text="{Binding Error.Message}" />
             <Button Content="Try Again"
                     Command="{Binding View.RefreshCommand}"
                     Grid.Column="1" />
     <DataTemplate x:Key="DataLoaderViewErrorTemplate">
             <StackPanel VerticalAlignment="Center"
                 <TextBlock Text="Something went wrong"
                             Margin="0,0,0,8" />
                 <TextBlock Text="Please try again."
                             TextAlignment="Center" />
                 <Button Content="Reload content"
                         Command="{Binding View.RefreshCommand}"
                         Margin="22,24,22,0" />
     <Style x:Key="DefaultDataLoaderViewStyle"
         <Setter Property="IsTabStop"
                 Value="False" />
         <Setter Property="HorizontalAlignment"
                 Value="Stretch" />
         <Setter Property="VerticalAlignment"
                 Value="Stretch" />
         <Setter Property="HorizontalContentAlignment"
                 Value="Stretch" />
         <Setter Property="VerticalContentAlignment"
                 Value="Stretch" />
         <Setter Property="EmptyTemplate"
                 Value="{StaticResource DataLoaderViewEmptyTemplate}" />
         <Setter Property="ErrorTemplate"
                 Value="{StaticResource DataLoaderViewErrorTemplate}" />
         <Setter Property="ErrorNotificationTemplate"
                 Value="{StaticResource DataLoaderViewErrorNotificationTemplate}" />
         <Setter Property="StateMinimumDuration"
                 Value="0:0:1.5" />
         <Setter Property="StateChangingThrottleDelay"
                 Value="0:0:0.100" />
         <Setter Property="Template">
                 <ControlTemplate TargetType="dl:DataLoaderView">
                             <VisualStateGroup x:Name="DataStates">
                                 <VisualState x:Name="Initial" />
                                 <VisualState x:Name="Data">
                                         <Setter Target="ContentPresenter.Visibility"
                                                 Value="Visible" />
                                 <VisualState x:Name="Empty" />
                             <VisualStateGroup x:Name="ErrorStates">
                                 <VisualState x:Name="NoError" />
                                 <VisualState x:Name="Error" />
                             <VisualStateGroup x:Name="LoadingStates">
                                 <VisualState x:Name="NotLoading" />
                                 <VisualState x:Name="Loading" >
                                         <Setter Target="LoadingIndicator.Visibility"
                                                 Value="Visible" />
                                         <Setter Target="LoadingIndicator.IsActive"
                                                 Value="True" />
                             <VisualStateGroup x:Name="CombinedStates">
                                 <VisualState x:Name="Initial_NoError_NotLoading" />
                                 <VisualState x:Name="Initial_NoError_Loading" />
                                 <VisualState x:Name="Initial_Error_NotLoading">
                                         <Setter Target="ErrorPresenter.Visibility"
                                                 Value="Visible" />
                                 <VisualState x:Name="Initial_Error_Loading">
                                         <Setter Target="ErrorPresenter.Visibility"
                                                 Value="Visible" />
                                 <VisualState x:Name="Data_NoError_NotLoading" />
                                 <VisualState x:Name="Data_NoError_Loading" />
                                 <VisualState x:Name="Data_Error_NotLoading">
                                         <Setter Target="ErrorNotificationPresenter.Visibility"
                                                 Value="Visible" />
                                 <VisualState x:Name="Data_Error_Loading">
                                         <Setter Target="ErrorNotificationPresenter.Visibility"
                                                 Value="Visible" />
                                 <VisualState x:Name="Empty_NoError_NotLoading">
                                         <Setter Target="EmptyPresenter.Visibility"
                                                 Value="Visible" />
                                 <VisualState x:Name="Empty_NoError_Loading" />
                                 <VisualState x:Name="Empty_Error_NotLoading">
                                         <Setter Target="ErrorNotificationPresenter.Visibility"
                                                 Value="Visible" />
                                 <VisualState x:Name="Empty_Error_Loading">
                                         <Setter Target="ErrorNotificationPresenter.Visibility"
                                                 Value="Visible" />
                         <ContentPresenter x:Name="ContentPresenter"
                                           Content="{TemplateBinding State}"
                                           ContentTemplate="{TemplateBinding ContentTemplate}"
                                           HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"
                                           VerticalAlignment="{TemplateBinding VerticalContentAlignment}"
                                           Padding="{TemplateBinding Padding}" />
                         <ContentPresenter x:Name="EmptyPresenter"
                                           Content="{TemplateBinding State}"
                                           ContentTemplate="{TemplateBinding EmptyTemplate}"
                                           HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"
                                           VerticalAlignment="{TemplateBinding VerticalContentAlignment}"
                                           Padding="{TemplateBinding Padding}" />
                         <ContentPresenter x:Name="ErrorPresenter"
                                           Content="{TemplateBinding State}"
                                           ContentTemplate="{TemplateBinding ErrorTemplate}"
                                           HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"
                                           VerticalAlignment="{TemplateBinding VerticalContentAlignment}"
                                           Padding="{TemplateBinding Padding}" />
                         <ContentPresenter x:Name="ErrorNotificationPresenter"
                                           Content="{TemplateBinding State}"
                                           ContentTemplate="{TemplateBinding ErrorNotificationTemplate}"
                                           HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"
                                           VerticalAlignment="{TemplateBinding VerticalContentAlignment}"
                                           Padding="{TemplateBinding Padding}" />
                         <ProgressRing x:Name="LoadingIndicator"
                                       VerticalAlignment="Center" />


  4. Add a DataLoaderView in your xaml.

    <dl:DataLoaderView Source="{Binding MyAsyncValue}"
                       Style="{StaticResource DefaultDataLoaderViewStyle}">
          <TextBlock Text="{Binding Data}" />
  5. Start your application! Note that by default using a DataLoaderView automatically triggers a initial load from the IDataLoader.


Load async data

The load function of the IDataLoader must simply return a Task of the data type (here MyData).

async Task<MyData> LoadData(CancellationToken ct, IDataLoaderRequest request)
  // Put your async operation here.
  return default(MyData);

This is where you would typically execute an API call or get data from any other async source.

This method receives a CancellationToken as the operation might be cancelled. Cancellation can happen for a few reasons.

  • When the IDataLoader is disposed.
  • If another request was made and the concurrent mode is CancelPrevious.

Get the DataLoader's state

You can check the state of a data loader using the IDataLoader.State property. You can observe its changes using the IDataLoader.StateChanged event.

The state of a DataLoader can be summarized as a combination of the following properties.

State Property Description
IsLoading True during the async load execution.
Data Last data from a successful request.
Error Error when the request failed.<br>Note: The error is cleared as soon as there is a successful request.

Imagine a scenario where you land on a page where the data has never been loaded before from an API.

  1. The system would first be on an initial state (not loading, no data, no error).
  2. The system would then start loading the data from the API.
  3. The system would then expose the data returned from the API.

This could be represented by the following state flow.

  direction LR
  s1: IsLoading(false)<br>Data(null)<br>Error(null)
  s2: <b>IsLoading(true)</b><br>Data(null)<br>Error(null)
  s3: IsLoading(false)<br><b>Data(myData)</b><br>Error(null)

  s1 --> s2 : Start loading
  s2 --> s3 : Receive data

Let's go deeper and imagine that we lose network and do a pull to refresh.

  1. You lose connection and refresh the page.
  2. The system would then start loading the data from the API.
  3. The system notifies you that there was an error, but you still have your previous data.

From the last sequence, we would continue with the following states.

  direction LR
  s3: IsLoading(false)<br>Data(myData)<br>Error(null)
  s4: <b>IsLoading(true)</b><br>Data(myData)<br>Error(null)
  s5: IsLoading(false)<br>Data(myData)<br><b>Error(WebException)</b>

  s3 --> s4 : Start refresh
  s4 --> s5 : Receive error<br>because not network

Other useful state properties are available:

State Property Description
IsInitial True by default. Becomes false when Data was set at least once.
IsEmpty This is always false unless you define the rule using IDataLoaderBuilder.IsEmptySelector.

Define IsEmpty

Apps often have a specific visual when content is empty. You can configure your DataLoader to evaluate the IDataLoaderState.IsEmpty property based on a predicate of your choice. Simply use IDataLoaderBuilder.WithEmptySelector.

MyAsyncList = DataLoaderBuilder<List<int>>
  .WithEmptySelector(state => state.Data is null || state.Data.Count == 0)


The DataLoaderView is the UI equivalent of a IDataLoader. It represents the different states of the IDataLoader using the following visual states. This is the list of all supported visual states and their respective visual state group.

Visual State Group Visual State
DataStates Initial
DataStates Data
DataStates Empty
ErrorStates NoError
ErrorStates Error
LoadingStates NotLoading
LoadingStates Loading
CombinedStates Initial_NoError_NotLoading
CombinedStates Initial_NoError_Loading
CombinedStates Initial_Error_NotLoading
CombinedStates Initial_Error_Loading
CombinedStates Data_NoError_NotLoading
CombinedStates Data_NoError_Loading
CombinedStates Data_Error_NotLoading
CombinedStates Data_Error_Loading
CombinedStates Empty_NoError_NotLoading
CombinedStates Empty_NoError_Loading
CombinedStates Empty_Error_NotLoading
CombinedStates Empty_Error_Loading

Here is the table of all possible visual state combinations.

DataStates ErrorStates LoadingStates CombinedStates
Initial NoError NotLoading Initial_NoError_NotLoading
Initial NoError Loading Initial_NoError_Loading
Initial Error NotLoading Initial_Error_NotLoading
Initial Error Loading Initial_Error_Loading
Data NoError NotLoading Data_NoError_NotLoading
Data NoError Loading Data_NoError_Loading
Data Error NotLoading Data_Error_NotLoading
Data Error Loading Data_Error_Loading
Empty NoError NotLoading Empty_NoError_NotLoading
Empty NoError Loading Empty_NoError_Loading
Empty Error NotLoading Empty_Error_NotLoading
Empty Error Loading Empty_Error_Loading

💡 You don't need to use all those states. It's possible to create a decent style without using the CombinedStates at all. The CombinedStates are available to offer support for advanced scenarios.

DataLoaderView also has a few template properties to more easily define its ControlTemplate. You can use any combination of the following in you styles. Remember that the source of truth comes from the visual states.

Template Suggested Usage
ContentTemplate Template used when there is data to show.
EmptyTemplate Template used when there is no data to show.
ErrorTemplate Template used when an error occurred.
ErrorNotificationTemplate Template used when an error occured but there is data to show.

💡 Again, you don't need to use all those properties. It's very possible that you don't use ErrorNotificationTemplate at all. Perhaps your style only uses ContentTemplate.

Protection against UI flickering

To avoid seeing flickery transitions between the different visual states, the DataLoaderView supports different throttling options.

  • StateMinimumDuration: This represents the minimum duration of a visual state. You should keep this high enough to prevent visual states from changing too fast. This is the property that prevents flickers.
  • StateChangingThrottleDelay: This represents the time before updating to a new state during which another update can happen. You should keep this low enough to prevent slowing down your user experience. This is the property that prevents seeing loading states that are not necessary.
<dl:DataLoaderView Source="{Binding MyDataLoader}"
                   StateChangingThrottleDelay="0:0:0.100" />


It's possible to add IDataLoaderTrigger objects to a DataLoader using IDataLoader.AddTrigger. This can be useful to automatically refresh the data. It also clearly indicates what are the dependencies of DataLoader.

There are a few implementations provided.

  • ManualDataLoaderTrigger: Manually triggers a load request.
  • ObservableDataLoaderTrigger: Triggers a load request when the observable pushes a new value.

There are some more implementations in the Chinook.DataLoader.DynamicMvvm package.

  • DynamicCommandDataLoaderTrigger: Triggers a load request when the IDynamicCommand.IsExecuting property changes.
  • DynamicPropertyDataLoaderTrigger: Triggers a load request when the value of a IDynamicProperty changes.

You can also create your own triggers by inheriting from DataLoaderTriggerBase. Simply call RaiseLoadRequested when a load request should be requested. You can also write a trigger from scratch by implementing IDataLoaderTrigger.

💡 DataLoaderView has a AutoLoad property which, as its name suggests, automatically requests an initial load from the DataLoader when it's displayed. This property defaults to true which means that you don't need to do anything to trigger the initial load when you use DataLoaderView.

Protection against concurrent loads

Now that we know what can trigger loads, we can see how it could be possible to request loads too fast and cause concurrent loads. The DataLoader doesn't allow concurrent loads. There are currently two behaviors to choose from when concurrent loads would happen.

  • CancelPrevious: When there's a new request while a previous one is already loading, the previous request gets cancelled. This is the default behavior.
  • DiscardNew: When there's a new request while a previous one is already loading, the new request gets discarded (it doesn't even start).

You can set the desired behavior using IDataLoaderBuilder.WithConcurrentMode.

Requests and contexts

To provide metadata on the loading operation, two important pieces are used.

  • IDataLoaderRequest: Represents the request to load data.
  • IDataLoaderContext: Contains user-defined key-value-pairs. It's exposed from the IDataLoaderRequest.

You can get or set additional information from the IDataLoader using the IDataLoaderRequest parameter.

Task<MyData> LoadData(CancellationToken ct, IDataLoaderRequest request)
  // This is the trigger that caused that loading operation.
  var sourceTrigger = request.SourceTrigger;

  // This is the context that was passed to the loading operation from the trigger.
  var context = request.Context;

  // You can read and write using the context.
  context["myMessage"] = "Hello!";

  // Your async operation here.

The request is also available as part of the IDataLoaderState and DataLoaderViewState. This means both request and context can be used in XAML data binding. This can be useful when implementing custom styles of DataLoaderView.

You can bind to the context from a style's ControlTemplate as follows.

<ControlTemplate TargetType="dl:DataLoaderView">
    <TextBlock Text="{Binding State.Request.Context[myMessage], RelativeSource={RelativeSource Mode=TemplatedParent}"/>

Triggers can also provide values through the context. Note however that the values provided by a trigger are only accessible from the load function when it originated from that trigger.

Integration with Chinook.DynamicMvvm

If you use Chinook.DynamicMvvm, know that there are built-in extensions methods that allow for fluent declaration of IDataLoader.

  1. Add the Chinook.DataLoader.DynamicMvvm package to your project.
  2. Register an IDataLoaderBuilderFactory in the IServiceProvider that your ViewModels use. Here is a simple code sample that does that using Microsoft.Extensions.DependencyInjection and Microsoft.Extensions.Hosting.
    var serviceProvider = new HostBuilder()
      .ConfigureServices(serviceCollection => serviceCollection
        .AddSingleton<IDataLoaderBuilderFactory, IDataLoaderBuilderFactory>()
  3. Use IViewModel.GetDataLoader to declare your DataLoader.
  4. Optionally use IViewModel.GetCommandFromDataLoaderRefresh if you want a command that refreshes the DataLoader. (This can be useful for things like pull-to-refresh.)
public class MyViewModel : ViewModelBase
  public IDynamicCommand RefreshData => this.GetCommandFromDataLoaderRefresh(Data);

  public IDataLoader Data => this.GetDataLoader(GetData, b => b
    // You can optionally configure your data loader here

  private async Task<MyData> GetData(CancellationToken ct)
    // Get data from your API...

💡 You can install the Visual Studio Extension Chinook Snippets and use code snippets to quickly generate DataLoader declarations when using Chinook.DynamicMvvm. All snippets related to IDataLoader start with ckdl (for Chinook DataLoader).

Automatically dispose previous data

Using IDataLoaderBuilder.DisposePreviousData, you can configure an IDataLoader that will automatically dispose its data when new data is loaded. This works when Data directly implements IDisposable or when it's an IEnumerable containing items implementing IDisposable.

public IDataLoader<DadJokesItemViewModel[]> Jokes => this.GetDataLoader(LoadJokes, b => b
    // Dispose the previous ItemViewModels when Jokes produces new values.

Automatically re-evaluate IsEmpty

Some types change on their own. A good example is ObservableCollection. DataLoader supports connecting to its Data in order to automatically update its state. Using IDataLoaderBuilder.UpdateOnCollectionChanged, you can configure an IDataLoader that will automatically re-evaluate IsEmpty when the collection changes. This works with any collection that implements INotifyCollectionChanged.

public IDataLoader<ObservableCollection<ToDoItem>> ToDoList => this.GetDataLoader(LoadToDoList, b => b
    // Re-evaluate is Empty when the collection changes.

For types that don't implement INotifyCollectionChanged, you can use IDataLoaderBuilder.SubscribeToData to implement an equivalent behavior.

⚙ Note that UpdateOnCollectionChanged is actually implemented using SubscribeToData. The SubscribeToData building block allows this kind of behavior for any type that is observable, meaning an object that exposes an event, implements or exposes IObservable<T>, or has any other subscription mechanism.

Automatically dispose subscriptions

You might need intermediate objects that needs disposing when loading data. A good example is the subscription when creating an observable collection using DynamicData.

public IDataLoader<ReadOnlyObservableCollection<int>> MyList => this.GetDataLoader(LoadMyList);

private async Task<ReadOnlyObservableCollection<int>> LoadMyList(CancellationToken ct, IDataLoaderRequest request)
  DynamicData.IObservableList<int> itemsSource = await GetItems(ct);
    .Bind(out var list)
    // Dispose this subscription when the next one is created.

  return list;

Using the IDisposable.DisposeWithNextLoad extensions method, you can ensure that only 1 disposable stays active at a time. Alternatively, you can use the IDataLoaderRequest.AddToSequenceDisposableGroup extension method which does the same thing.

Note that even when there are no subsequent loads, the disposable still gets disposed when the IDataLoader itself gets disposed.

Load on a background thread

Using IDataLoaderBuilder.OnBackgroundThread, you can configure an IDataLoader that will invoke its load function from Task.Run. This can be helpful to avoid loading data on the UI thread.

public IDataLoader<string> Stuff => this.GetDataLoader(LoadStuff, b => b
    // Invoke the load from a new task.

Define default behaviors

Using DataLoaderBuilderFactory, you can create a IDataLoaderBuilderFactory that provides default behaviors in all the IDataLoaderBuilder instances it creates. Here you can see how to create an IDataLoaderBuilderFactory using Microsoft.Extensions.DependencyInjection.

private static IServiceCollection AddDataLoaderFactory(this IServiceCollection services)
  return services.AddSingleton<IDataLoaderBuilderFactory>(s =>
    return new DataLoaderBuilderFactory(b => b

    bool GetIsEmpty(IDataLoaderState state)
      return state.Data == null || (state.Data is IEnumerable enumerable &&    !enumerable.Cast<object>().Any());

💡 When using Chinook.DynamicMvvm, the IViewModel.GetDataLoader extension methods automatically use IDataLoaderBuilderFactory registered in the IServiceProvider to generate the IDataLoader instances.

Support for custom behaviors

The architecture of IDataLoader and IDataLoaderBuilder was made in a way that more custom behaviors can be implemented. Using IDataLoaderBuilder.DelegatingStrategies, you can add processing both before and after the actual load function in the same fashion as you would using a stack of System.Net.Http.HttpMessageHandler. Combining this with triggers, IDataLoaderRequest, and IDataLoaderContext, brings a lot of flexibility because the strategy has access to the request and context objects.

⚙ Even the recipes we've seen so far (like SubscribeToData or DisposeWithNextLoad) are built on top of that extensible foundation.

Configure a default refresh command for all DataLoaderViews

It's possible to configure a refresh command for all DataLoaderView instances using DataLoaderView.DefaultRefreshCommandProvider. When this property is set, it's used to set an initial value to DataLoaderView.RefreshCommand.

This can be useful to avoid repeating the same code in ViewModels. It's also a great way to ensure all DataLoaderViews support manual refreshes, which enables things like putting a refresh button in you DataLoaderView's ControlTemplate.

Here is an example to demonstrate how to use DataLoaderView.DefaultRefreshCommandProvider. In this example, we leverage Chinook.DynamicMvvm to build the command.

private void SetupDefaultRefreshCommand(IServiceProvider services)
  // DefaultRefreshCommandProvider is just a Func<DataLoaderView, ICommand> that's invoked when a DataLoaderView is created.
  DataLoaderView.DefaultRefreshCommandProvider = GetDataLoaderViewRefreshCommand;

  ICommand GetDataLoaderViewRefreshCommand(DataLoaderView dataLoaderView)
    return services
        name: "DataLoaderViewRefreshCommand",
        execute: async (ct) =>
          var context = new DataLoaderContext();
          // You can add some content to the context.
          context["IsForceRefreshing"] = true;
          await dataLoaderView.DataLoader.Load(ct, context);
        viewModel: (IViewModel)App.Instance.Shell.DataContext)

Breaking Changes

Please consult for more information about breaking changes and version history.


This project is licensed under the Apache 2.0 license - see the LICENSE file for details.


Please read for details on the process for contributing to this project.

Be mindful of our Code of Conduct.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed.  monoandroid11.0 is compatible.  monoandroid12.0 is compatible. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Universal Windows Platform uap10.0.19041 is compatible. 
Xamarin.iOS xamarinios was computed.  xamarinios10 is compatible. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.2.1-feature.Uno5Update.2 173 11/3/2023
1.2.0 36,011 11/22/2022
1.1.2 832 11/1/2022
1.1.1 497 10/12/2022
1.1.0 1,107 9/22/2022
1.1.0-feature.dotnet6.2 128 9/22/2022
1.1.0-feature.dotnet6.1 103 9/21/2022
1.0.0 6,017 8/30/2022
0.10.0 477 8/25/2022
0.10.0-dev.91 357 8/9/2022
0.10.0-dev.89 332 8/4/2022 174 3/15/2022
0.7.0-dev.87 19,624 5/25/2022
0.7.0-dev.85 130 5/25/2022
0.7.0-dev.83 6,588 5/19/2022
0.7.0-dev.81 139 5/17/2022
0.7.0-dev.79 155 5/13/2022
0.6.0-dev.77 160 5/2/2022
0.6.0-dev.76 4,464 3/31/2022 130 3/15/2022 128 3/15/2022 135 3/15/2022
0.5.0-dev.73 269 3/15/2022 4,225 12/21/2021
0.4.0-dev.69 17,859 11/26/2021
0.3.0-dev.67 11,190 10/4/2021
0.3.0-dev.65 767 9/21/2021
0.3.0-dev.63 1,962 9/13/2021
0.3.0-dev.60 779 8/30/2021
0.3.0-dev.58 2,063 7/26/2021
0.3.0-dev.56 2,075 7/5/2021
0.3.0-dev.54 12,126 6/22/2021
0.3.0-dev.52 458 6/19/2021
0.3.0-dev.50 259 6/5/2021
0.3.0-dev.48 1,578 4/20/2021
0.3.0-dev.44 19,276 4/8/2021
0.3.0-dev.42 6,514 3/16/2021
0.2.0-dev.37 1,811 12/17/2020
0.2.0-dev.35 2,890 11/2/2020
0.2.0-dev.33 2,855 10/27/2020
0.2.0-dev.31 236 10/13/2020
0.2.0-dev.29 236 9/29/2020
0.2.0-dev.27 6,896 8/13/2020
0.2.0-dev.25 273 6/26/2020