Deploying .NET MAUI Apps - Microsoft Docs

Introduction to .NET MAUI Deployment

This document provides a comprehensive guide to deploying your .NET MAUI (Multi-platform App UI) applications across various target platforms. .NET MAUI simplifies the process of building native applications for Windows, macOS, Android, and iOS from a single, shared codebase.

Deployment strategies can vary significantly depending on the target platform and your chosen distribution method. We will cover common scenarios and best practices.

Platform-Specific Deployment

Windows Deployment

For Windows, you can deploy your .NET MAUI application using several methods:

MSIX Packaging: This is the modern packaging format for Windows applications, offering a robust and streamlined deployment experience. It supports auto-updates, rollback, and a clean uninstall process.
ClickOnce: A deployment technology that enables developers to deploy and update applications easily.
Self-Contained Deployment: Distribute your application without requiring users to install the .NET runtime separately.

To create an MSIX package, you can use Visual Studio's built-in packaging tools or the MAUI workload commands.

dotnet publish -f net8.0-windows10.0.19041.0 -c Release -p:PublishProfile=AppxPackage

macOS Deployment

On macOS, .NET MAUI applications can be deployed as:

DMG (Disk Image): The standard distribution format for macOS applications.
App Store: Distribute your application through the Mac App Store for broad reach and simplified updates.

Creating a DMG typically involves signing your application and then using tools like hdiutil.

dotnet publish -f net8.0-maccatalyst -c Release
# Further steps for packaging and signing would follow

Android Deployment

Deploying to Android involves creating an APK (Android Package) or an AAB (Android App Bundle):

APK: The traditional package format for Android applications.
AAB: The recommended format for publishing to the Google Play Store. It allows Google Play to optimize app delivery for different devices.

You will need to sign your application with a release key.

dotnet publish -f net8.0-android -c Release -p:AndroidPackageFormat=aab
# Signing instructions will be required for distribution

iOS Deployment

For iOS, deployment typically involves:

Ad Hoc Distribution: For testing with a limited set of devices.
App Store Distribution: Publishing to the Apple App Store.
Enterprise Distribution: For internal distribution within an organization.

Deployment to iOS requires provisioning profiles and certificates managed through your Apple Developer account.

dotnet publish -f net8.0-ios -c Release -p:RuntimeIdentifier=ios-arm64
# Further steps for archiving, signing, and distribution are platform-specific

General Deployment Considerations

Code Signing

Code signing is crucial for security and trust on all platforms. It verifies the authenticity of your application and ensures it hasn't been tampered with.

Release Configuration

Always build your application in the Release configuration for optimized performance and smaller deployment sizes.

Application Icons and Splash Screens

Ensure your application has correctly sized and formatted icons and splash screens for each target platform to provide a professional user experience.

Testing

Thoroughly test your application on all target devices and operating system versions before deploying to production. Utilize simulators, emulators, and physical devices.