Migrating to 2026 August
Introduction
This page discusses breaking changes and other considerations when migrating from 2026 July to 2026 August.
What Changed at a Glance
2026 August ships two changes. GraphicalUiElement's GetAbsoluteWidth() and GetAbsoluteHeight() methods become the AbsoluteWidth and AbsoluteHeight properties, matching the existing AbsoluteLeft, AbsoluteTop, AbsoluteRight, and AbsoluteBottom properties. This is a soft break: the old methods still compile and work, but now emit a CS0618 obsolete warning.
Separately, MonoGameGum.csproj's iOS and Android target frameworks change from opt-out to opt-in. This affects you only if you reference the MonoGameGum source project directly. Nothing changes if you use the Gum.MonoGame NuGet package.
Upgrading the Gum Tool
To upgrade the Gum tool:
Download Gum.zip from the August 3, 2026 release on GitHub
Delete the old tool from your machine
Unzip the gum tool to the same location as to not break any file associations
Run the upgrade gum upgrade or ~/bin/gum upgrade
Upgrading the Runtime
This release's runtime ships as NuGet version 2026.8.3.1. Upgrade your Gum NuGet packages to this version. For more information, see the NuGet packages for your particular platform:
MonoGame - https://www.nuget.org/packages/Gum.MonoGame/
SkiaSharp - https://www.nuget.org/packages/Gum.SkiaSharp/
If using GumCommon directly, you can update the GumCommon NuGet:
Breaking Changes and Migrations
GetAbsoluteWidth() / GetAbsoluteHeight() Renamed to AbsoluteWidth / AbsoluteHeight
GraphicalUiElement exposes the final, computed pixel dimensions of an element (as opposed to its authored WidthUnits/HeightUnits-relative values) through two methods, GetAbsoluteWidth() and GetAbsoluteHeight(). These are now properties, AbsoluteWidth and AbsoluteHeight, matching the naming of the existing AbsoluteLeft, AbsoluteTop, AbsoluteRight, and AbsoluteBottom properties.
The old methods still compile and work, but now emit a CS0618 warning:
To migrate, replace the method call with the property at your call sites:
❌ Old:
✅ New:
MonoGameGum's iOS and Android Target Frameworks Are Now Opt-In
This section applies only if you reference MonoGameGum.csproj directly (source linking). If you use the Gum.MonoGame NuGet package, you can skip it: the published package still ships both mobile target frameworks and nothing changes for you.
MonoGameGum.csproj used to build its iOS and Android target frameworks by default, with ExcludeIOS and ExcludeAndroid properties available to turn them off. Those properties did not propagate through a ProjectReference from your own project, so on a .NET 9 or newer SDK every desktop-only source-linked build pulled in net9.0-ios and net9.0-android and failed with mobile workload errors that had no project-level fix.
The flags are now opt-in, matching KniGum.csproj:
ExcludeIOS
IncludeIOS
ExcludeAndroid
IncludeAndroid
Desktop-only builds now work with no flags at all. If you were deliberately building the mobile target frameworks from source, pass the new properties on the command line or as environment variables:
Setting them inside your own .csproj does not work. Only real global properties propagate through a ProjectReference.
Last updated
Was this helpful?

