This article explains how to build Uno.UI locally, for instance if you wish to contribute a bugfix or new feature.
- Visual Studio 2019 (16.6 or later)
Mobile Development with .NET(Xamarin) development
Visual Studio extensions development(for the VSIX projects)
ASP.NET and Web Development
.NET Core cross-platform development
UWP Development, install all recent UWP SDKs, starting from 10.0.14393 (or above or equal to
TargetPlatformVersionline in this file)
- Install (Tools / Android / Android SDK manager) all Android SDKs starting from 7.1 (or the Android versions
TargetFrameworkslist used here)
Building Uno.UI for a single target platform
This is the recommended approach to building the Uno.UI solution. It will build a single set of binaries for a particular platform (eg Android, iOS, WebAssembly, etc).
Building for a single target platform is considerably faster, much less RAM-intensive, and generally more reliable.
It involves two things - setting an override for the target framework that will be picked up by the (normally multi-targeted) projects inside the Uno solution; and opening a preconfigured solution filter which will only load the projects needed for the current platform.
The step by step process is:
- Clone the Uno.UI repository locally, and ensure using a short target path, e.g. D:\uno etc.
This is due to limitations in the legacy .NET versions used by Xamarin projects. This issue has been addressed in .NET 5, and will come to the rest of the projects in the future.
- Make sure you don't have the Uno.UI solution open in any Visual Studio instances. (Visual Studio may crash or behave inconsistently if it's open when the target override is changed.)
- Make a copy of the src/crosstargeting_override.props.sample file and name this copy
crosstargeting_override.props, uncomment the line
- Set the build target inside
<UnoTargetFrameworkOverride></UnoTargetFrameworkOverride>to the identifier for the target platform you wish to build for. (Identifiers for each platform are listed in the file.) Save the file.
- In the
srcfolder, look for the solution filter (
.slnffile) corresponding to the target platform override you've set, which will be named
Uno.UI-[Platform]-only.slnf, and open it.
- To confirm that everything works:
- For iOS/Android/macOS you can right-click on the
Uno.UIproject in the Solution Explorer and 'Build'.
- For WebAssembly and Skia you can right-click on the
Uno.UI.Runtime.Skia.[Gtk|Wpf]project in the Solution Explorer and 'Build'.
Once you've built successfully, for the next steps, consult the guide here for debugging Uno.UI.
If you've followed the steps above, you have your environment set up with the listed prerequisites, and you still encounter errors when you try to build the solution, you can reach out to the core team on Uno's Discord channel #uno-platform.
Windows and long paths issues
If the build tells you that
LongPath is not enabled, you may enable it on Windows 10 by using :
reg ADD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem /v LongPathsEnabled /t REG_DWORD /d 1
If for some reason you cannot modify the registry, you can disable this warning by adding
<UnoUIDisableLongPathWarning>false</UnoUIDisableLongPathWarning> to the project.
Note that long paths may be required when building Uno, and invalid paths errors may arise.
Building Uno.UI for all available targets
It's recommended to build using the single-target approach, but it's also possible to build for all targets at once, if you wish.
- If you've previously followed the single-target steps, comment out the
<UnoTargetFrameworkOverride />line in your
- Open the Uno.UI.sln
- Select the
Inside Visual Studio, the number of platforms is restricted to limit the compilation time.
Building Uno.UI for macOS using Visual Studio for Mac
See instructions here for building Uno.UI for the macOS platform.
Other build-related topics
Using the Package Diff tool
Refer to the guidelines for breaking changes document.
Updating the Nuget packages used by the Uno.UI solution
The versions used are centralized in the Directory.Build.targets file, and all the
<PackageReference /> are used.
When updating the versions of nuget packages, make sure to update all the .nuspec files in the Build folder.