ControlR.Viewer.Avalonia 0.22.79

ControlR.Viewer.Avalonia

ControlR.Viewer.Avalonia provides the ControlrViewer control for embedding a ControlR remote viewer inside an Avalonia UI application.

Use it when you want to host a live ControlR session inside one of your existing views (not necessarily your main window).

Install

dotnet add package ControlR.Viewer.Avalonia

Requirements

Your view model must expose a ControlrViewerOptions instance containing:

• BaseUrl (Uri) - Base URL of your ControlR server.
• DeviceId (Guid) - Device to connect to.
• PersonalAccessToken (string) - PAT for the connecting user.

How those values are resolved is up to your application architecture.

Core APIs

ControlrViewer exposes these primary bindable/public members:

• Options (ControlrViewerOptions?) - connection settings for the viewer instance.
• Page (ViewerPage) - declaratively selects the active page.
• InstanceId (Guid) - unique ID assigned to the viewer instance after construction.
• GetInstanceInfo() - returns the public-facing ViewerInstanceInfo for this viewer instance.
• GetRequiredService<T>() - resolves a required service from this viewer instance.
• GetService<T>() - resolves an optional service from this viewer instance.

Available ViewerPage values:

• None
• RemoteControl
• FileSystem
• Terminal

Usage Example

In this example, ControlrViewer is hosted in ParentView.axaml, with options provided by ParentViewModel.

ParentView.axaml

<UserControl xmlns="https://github.com/avaloniaui"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             xmlns:vm="using:YourApp.ViewModels"
             xmlns:ctrlr="using:ControlR.Viewer.Avalonia"
             xmlns:nav="using:ControlR.Viewer.Avalonia.Services.Navigation"
             x:Class="YourApp.Views.ParentView"
             x:DataType="vm:ParentViewModel">

	<ctrlr:ControlrViewer Options="{Binding ViewerOptions}"
	                     Page="{Binding CurrentPage}" />
</UserControl>

ParentViewModel.cs

using ControlR.Libraries.Viewer.Common.Options;
using ControlR.Viewer.Avalonia.Services.Navigation;
using Microsoft.Extensions.Options;

namespace YourApp.ViewModels;

public class ParentViewModel
{
  public ParentViewModel(IOptions<ControlrViewerOptions> viewerOptions)
  {
    ViewerOptions = viewerOptions.Value;
  }

  public ViewerPage CurrentPage { get; set; } = ViewerPage.RemoteControl;
  public ControlrViewerOptions ViewerOptions { get; }
}

Declarative Navigation

Set the Page property to control which page the embedded viewer should display.

<ctrlr:ControlrViewer Options="{Binding ViewerOptions}"
                     Page="{Binding CurrentPage}" />

CurrentPage = ViewerPage.FileSystem;

If the viewer is not fully connected yet, the requested page is stored and applied once navigation becomes available.

Imperative Navigation

For imperative page changes, resolve INavigator from the viewer instance and call NavigateTo.

using ControlR.Viewer.Avalonia.Services.Navigation;

var navigator = controlrViewer.GetInstanceInfo().GetNavigator();
var result = await navigator.NavigateTo(ViewerPage.Terminal);

if (!result.IsSuccess)
{
  // Handle result.Reason.
}

You can also get INavigator through ViewerRegistry or ViewerInstanceInfo if you are operating from outside the control tree.

ViewerRegistry

The library exposes a global ViewerRegistry helper (in ControlR.Viewer.Avalonia.Services) that stores information about the ControlrViewer and IServiceProvider instances that are currently active. This allows you to interact with the viewers and their services from anywhere in your application, as long as you have the viewer's instance ID (which is a Guid).

Instances are automatically registered when a ControlrViewer is initialized and unregistered/disposed when the ControlrViewer instance is detached from the visual tree, so you don't need to manage the lifecycle manually.

Important APIs:

• ViewerRegistry.Register(Guid instanceId, ControlrViewer viewer, IServiceProvider serviceProvider) — registers a viewer instance (the control registers itself automatically).
• ViewerRegistry.Unregister(Guid instanceId) — removes a registered instance (the control unregisters itself on disposal).
• ViewerRegistry.GetRequiredService<T>(Guid instanceId) — resolves a required service from a specific viewer's scope and throws if not found.
• ViewerRegistry.GetService<T>(Guid instanceId) — attempts to resolve a service and returns null if not found.
• ViewerRegistry.GetService(Guid instanceId, Type serviceType) — non-generic service resolution.
• ViewerRegistry.GetAllInstanceIds() — returns all currently registered viewer instance IDs.
• ViewerRegistry.TryGetInstance(Guid instanceId, out ViewerInstanceInfo? viewerInstanceInfo) — attempts to get a registered viewer instance plus its service provider.

ViewerInstanceInfo exposes:

• InstanceId
• Viewer
• ServiceProvider
• GetHubConnection()
• GetControlrApi()
• GetNavigator()

Example usage:

using ControlR.Viewer.Avalonia.Services;
using ControlR.Viewer.Avalonia.Services.Navigation;

if (ViewerRegistry.TryGetInstance(viewerId, out var instance))
{
  var navigator = instance.GetNavigator();
  await navigator.NavigateTo(ViewerPage.FileSystem);

  var api = instance.GetControlrApi();
  var hubConnection = instance.GetHubConnection();
}

You can also resolve arbitrary services directly:

var remoteControlStream = ViewerRegistry.GetRequiredService<IViewerRemoteControlStream>(viewerId);

Notes

• Keep PATs out of source control.
• The ControlrViewer initializes and connects to the server once it becomes visible.
• Options will be validated automatically before connecting.
  • If any options are missing or invalid, the control will render an error message instead.
• Viewer instances register themselves with ViewerRegistry after their internal service provider is built.
• Page defaults to ViewerPage.None.