Migrating to Uno Platform 6.0

Uno Platform 6.0 contains some breaking changes required to provide a consistent experience when using the Skia rendering feature, as well as the removal of the UWP API set support and the removal of the GTK desktop runtime support.

You can find a list of these changes below.

Removal of the UWP API Set

Uno Platform started off with UWP as the common API set, then added WinUI/WinAppSDK. Both API sets were kept as a convenience for upgrading to WinUI, and now that WinUI is sufficiently advanced, Uno Platform 6.0 removes the UWP API set entirely.

This makes Uno Platform easier to maintain in the long run and easier to contribute to.

If you're still using the UWP API set, you can see our migration guides on how to move to WinUI.

Removal of Skia GTK Desktop support

Over the years, we've provided desktop platform abstractions through different technologies. While desktop support started with a GTK3 shell as a common ground, Uno Platform 5.6 introduced specialized shell support for X11, WPF, and AppKit.

Now that the support for these targets is stable, we're removing the support for the GTK shell for projects that have not yet used the Uno.SDK.

If your project is still using the GTK support, you can keep using Uno Platform 5.6, or migrate to the Uno.SDK style project, which uses the latest platform support, including the new Win32 shell feature.

List of common manual changes for Uno Platform 6.0

Updating the Desktop Builder

Upgrading the Desktop platform builder is required when moving to Uno Platform 6.0, in order to align builders for all platforms, for all renderers.

To upgrade, in your Platforms/Desktop/Program.cs:

• Replace using Uno.UI.Runtime.Skia; with using Uno.UI.Hosting;
• Replace SkiaHostBuilder with UnoPlatformHostBuilder

Use the new Win32 desktop support

Uno Platform 6.0 provides support for a new, faster, and leaner Windows support, which does not depend on additional libraries (like WPF in previous Uno Platform versions). This new support also enables IL, XAML, and Resource Trimming for smaller published app packages.

To upgrade to the Win32 support, in your Platforms/Desktop/Program.cs, replace .UseWindows() with .UseWin32().

WinAppSDK 1.7 considerations

Uno Platform 6 updates to WinAppSDK 1.7 when using the Uno.SDK.

If you encounter the following build error:

error CS1705: Assembly 'Assembly_Name' with identity 'Assembly_Name, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null' uses 'WinRT.Runtime, Version=2.2.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709' which has a higher version than referenced assembly 'WinRT.Runtime' with identity 'WinRT.Runtime, Version=2.1.0.0, Culture=neutral, PublicKeyToken=99ea127f02d97709'

This may be due to a mismatch in the Windows SDK version used by your project.

To fix this issue, add the following to your .csproj file to ensure the correct Windows SDK is referenced for the net9.0-windowsXX target to build properly:

<PropertyGroup>
    <WindowsSdkPackageVersion>10.0.19041.57</WindowsSdkPackageVersion>
</PropertyGroup>

Uno Extensions

Uno Platform 6.0 introduces a breaking change to the Http Uno Feature:

• The existing Http feature still exists, but no longer includes the Uno.Extensions.Http.Refit package by default.
• Two new features have been added:
  • HttpRefit – Configures Uno.Extensions.Http.Refit so you can register and consume REST APIs using Refit’s type-safe client generation.
  • HttpKiota – Configures Uno.Extensions.Http.Kiota so you can register and consume OpenAPI-defined endpoints using Kiota’s HTTP client generator.

Note

If you’re upgrading and previously relied on Refit from the Http feature, remove Http from your <UnoFeatures> and add HttpRefit instead. See the HTTP overview for more information.

Optional use of Skia Rendering for iOS, Android, and WebAssembly

In order to use Skia Rendering for these targets, we're adding new APIs that make the bootstrapping of iOS and WebAssembly platforms using common builders.

To upgrade:

• Make sure that your project is using the Uno.SDK.

• In your .csproj, add the following to enable Skia rendering:

  <UnoFeatures>
  <!-- Existing features -->
  +  SkiaRenderer;
  </UnoFeatures>
  

• In your Platforms/WebAssembly/Program.cs change this:

  public static int Main(string[] args)
  {
      App.InitializeLogging();
  
      Microsoft.UI.Xaml.Application.Start(_ => _app = new App());
  
      return 0;
  }
  

  with the following:

  using Uno.UI.Hosting;
  
  ...
  
  public static async Task Main(string[] args)
  {
      App.InitializeLogging();
  
      var host = UnoPlatformHostBuilder.Create()
          .App(() => new App())
          .UseWebAssembly()
          .Build();
  
      await host.RunAsync();
  }
  

  If your startup code contained a static _app field, you can remove it as well. You can also use the top-level program code, as found in the default Uno Platform templates.

• In your Platforms/iOS/Main.iOS.cs change the following:

  using UIKit;
  
  ...
  
  public static void Main(string[] args)
  {
      UIApplication.Main(args, null, typeof(App));
  }
  

  with the following:

  using Uno.UI.Hosting;
  
  ...
  
  public static void Main(string[] args)
  {
      App.InitializeLogging();
  
      var host = UnoPlatformHostBuilder.Create()
          .App(() => new App())
          .UseAppleUIKit()
          .Build();
  
      host.Run();
  }
  

  You can also use the top-level program code, as found in the default Uno Platform templates.

• In your Platforms/Android/Main.Android.cs, change the following:

  public Application(IntPtr javaReference, JniHandleOwnership transfer)
      : base(() => new App(), javaReference, transfer)
  {
  -    ConfigureUniversalImageLoader();
  }
  
  -private static void ConfigureUniversalImageLoader()
  -{
  -    var config = new ImageLoaderConfiguration.Builder(Context).Build();
  -    ImageLoader.Instance.Init(config);
  -    ImageSource.DefaultImageLoader = ImageLoader.Instance.LoadImageAsync;
  -}
  

  Uno Platform handles image loading entirely with the Skia Rendering mode.