{"id":40587,"date":"2022-06-28T10:34:21","date_gmt":"2022-06-28T17:34:21","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=40587"},"modified":"2022-06-27T15:34:53","modified_gmt":"2022-06-27T22:34:53","slug":"devops-for-dotnet-maui","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/devops-for-dotnet-maui\/","title":{"rendered":"Getting Started with DevOps and .NET MAUI"},"content":{"rendered":"<p><a href=\"https:\/\/dot.net\/maui\">.NET Multi-platform App UI (.NET MAUI)<\/a> unifies Android, iOS, macOS, and Windows UI frameworks into a single framework so you can write one app that runs natively on many platforms. In this post, we will look at how easy it is to implement basic DevOps pipelines for .NET MAUI apps using GitHub Actions and Azure DevOps.<\/p>\n<h2>Getting Started<\/h2>\n<p>Before setting up the pipelines, we need to make sure we have a few files ready.<\/p>\n<ul>\n<li>For <code>iOS<\/code>, you need a signing certificate and a provisioning profile. This <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/apps\/mobile\/app-signing?view=azure-devops&amp;tabs=apple-install-during-build#apple\">guide<\/a> walks you through how to obtain these files.<\/li>\n<li>(Optional for this post) For <code>Android<\/code>, you need keystore file and value of keystore password and keystore alias. This <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/apps\/mobile\/app-signing?view=azure-devops&amp;tabs=apple-install-during-build#sign-your-android-app\">guide<\/a> walks you through how to obtain the files.<\/li>\n<li>For <code>Windows<\/code>, you need to create and export a certificate for package signing. You can follow this <a href=\"https:\/\/docs.microsoft.com\/windows\/msix\/package\/create-certificate-package-signing\">guide<\/a> for the steps.<\/li>\n<\/ul>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2022\/06\/prereq_files.png\" alt=\"list of files required for pipelines\" \/><\/p>\n<p>We are now ready to start creating the pipelines for the .NET MAUI app. We will be looking at the sample pipelines added to the <a href=\"https:\/\/github.com\/dotnet\/maui-samples\">dotnet\/maui-samples<\/a> repo as part of the Weather21 app, under the folder <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/tree\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\">devops<\/a>.<\/p>\n<h3>Pipeline Source Files<\/h3>\n<blockquote>\n<p><strong>NOTE<\/strong> <em>These are starter pipelines for a basic test and build, great to use for PR-checks. The steps do not cover publish to store or signing for distribution. That would be out of scope for this post, and will be covered in a future post.<\/em><\/p>\n<\/blockquote>\n<h4>GitHub Actions Samples<\/h4>\n<ul>\n<li>MacOS Hosted Agent : <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/GitHubActions\/macos-build.yml\">macos-build.yml<\/a><\/li>\n<li>Windows Hosted Agent: <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/GitHubActions\/windowsCI.yml\">windowsCI.yml<\/a><\/li>\n<\/ul>\n<h4>Azure DevOps Samples<\/h4>\n<ul>\n<li>MacOS Hosted Agent : <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/AzureDevOps\/azdo_mac.yml\">azdo_mac.yml<\/a><\/li>\n<li>Windows Hosted Agent: <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/AzureDevOps\/azdo_windows.yml\">azdo_windows.yml<\/a><\/li>\n<\/ul>\n<h3>Pipeline Overview<\/h3>\n<p>We have 2 pipeline files for both GitHub Actions and Azure DevOps, one runs on the <code>macos-12<\/code> VM building the <code>iOS<\/code> and <code>MacCatalyst<\/code> targets. The other runs on <code>windows-2022<\/code> VM and builds the <code>Android<\/code> and <code>Windows<\/code> targets.<\/p>\n<p>Each Pipeline is broken down into the follow sub-steps:<\/p>\n<ol>\n<li>Set .NET Version<\/li>\n<li>Install .NET MAUI Workloads<\/li>\n<li>Install Signing Files (as needed)<\/li>\n<li>Build\/Publish App for TargetFramework<\/li>\n<li>Run Unit Tests (if required)<\/li>\n<li>Upload Artifacts<\/li>\n<\/ol>\n<p>This simplified DevOps flow is all thanks to <code>dotnet<\/code> command line tool which we have access to now. We are able to <code>dotnet build<\/code> and <code>dotnet publish<\/code> for all TargetFramework types. No need for complex and convoluted scripts to manage <code>msbuild<\/code> and <code>VS preview<\/code> installations. Thank you to all the contributors for making this happen!<\/p>\n<p>Let&#8217;s break down the tasks in each Pipeline.<\/p>\n<h2>Pipeline Tasks<\/h2>\n<blockquote>\n<p><strong>Quick Tip<\/strong> Check available GitHub hosted VM images and installed software by checking this <a href=\"https:\/\/github.com\/actions\/virtual-environments#available-environments\">table<\/a>.<\/p>\n<\/blockquote>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2022\/06\/github_actions.png\" alt=\"summary of completed github actions pipeline\" \/><\/p>\n<blockquote>\n<p><strong>Quick Tip<\/strong> Check available Azure DevOps hosted VM images and installed software by checking this <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/agents\/hosted?view=azure-devops&amp;tabs=yaml#software\">table<\/a>.<\/p>\n<\/blockquote>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2022\/06\/azure_devops.png\" alt=\"summary of completed azure devops pipeline\" \/><\/p>\n<p>The common tasks for both pipelines are <code>Setup .NET SDK Version<\/code> and <code>Install .NET MAUI<\/code>.<\/p>\n<p>This is how it looks like in <code>GitHub Actions<\/code>:<\/p>\n<pre><code class=\"language-yml\">\r\n      - name: Setup .NET SDK ${{env.DOTNETVERSION}}\r\n        uses: actions\/setup-dotnet@v1\r\n        with:\r\n          dotnet-version:  '${{env.DOTNETVERSION}}'\r\n\r\n      - name: Install .NET MAUI\r\n        shell: bash\r\n        run: |\r\n          dotnet nuget locals all --clear \r\n          dotnet workload install maui --source https:\/\/aka.ms\/dotnet6\/nuget\/index.json --source https:\/\/api.nuget.org\/v3\/index.json\r\n          dotnet workload install android ios maccatalyst tvos macos maui wasm-tools --source https:\/\/aka.ms\/dotnet6\/nuget\/index.json --source https:\/\/api.nuget.org\/v3\/index.json\r\n<\/code><\/pre>\n<p>The first task uses the GitHub Action <a href=\"https:\/\/github.com\/marketplace\/actions\/setup-net-core-sdk\">Setup .NET Core SDK<\/a> and the creating a pipeline variable makes it easier to change versions in the future.<\/p>\n<p>This is how it looks like in <code>Azure DevOps<\/code> :<\/p>\n<pre><code class=\"language-yml\">\r\n    - task: UseDotNet@2\r\n      displayName: .NET Version\r\n      inputs:\r\n        packageType: 'sdk'\r\n        version: '$(DotNetVersion)'\r\n\r\n    - task: Bash@3\r\n      displayName: Install MAUI\r\n      inputs:\r\n        targetType: 'inline'\r\n        script: |\r\n          dotnet nuget locals all --clear \r\n          dotnet workload install maui --source https:\/\/aka.ms\/dotnet6\/nuget\/index.json --source https:\/\/api.nuget.org\/v3\/index.json\r\n          dotnet workload install android ios maccatalyst tvos macos maui wasm-tools --source https:\/\/aka.ms\/dotnet6\/nuget\/index.json --source https:\/\/api.nuget.org\/v3\/index.json\r\n<\/code><\/pre>\n<p>The first task uses the Azure Devops <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/tool\/dotnet-core-tool-installer?view=azure-devops\">Use .NET Core task<\/a> and the creating a pipeline variable makes it easier to change versions in the future.<\/p>\n<p>The next task is <code>Install .NET MAUI workloads<\/code> via inline script. You can adjust the <code>--source<\/code> to target specific versions of .NET MAUI workloads, and you can learn more about changing sources in the <a href=\"https:\/\/github.com\/dotnet\/maui\/wiki\/macOS-Install#install-net-6-with-net-maui\">.NET MAUI Wiki<\/a>.<\/p>\n<h3>Mac Build Agent Pipeline<\/h3>\n<p>The build\/publish task is explained in the .NET MAUI Documentation:<\/p>\n<ul>\n<li><a href=\"https:\/\/docs.microsoft.com\/dotnet\/maui\/macos\/deployment\/overview\">Publish MacCatalyst App<\/a><\/li>\n<li><a href=\"https:\/\/docs.microsoft.com\/dotnet\/maui\/ios\/deployment\/overview\">Publish iOS App<\/a><\/li>\n<\/ul>\n<p>For example, the Publish MacCatalyst task in <code>GitHub Actions<\/code> :<\/p>\n<pre><code class=\"language-yml\">\r\n - name : Publish MacCatalyst App\r\n        shell: bash\r\n        run: |\r\n          cd 6.0\/Apps\/WeatherTwentyOne\/src\r\n          dotnet publish -f net6.0-maccatalyst -c Release -p:BuildIpa=True -o .\/artifacts\r\n<\/code><\/pre>\n<p>and the same task in <code>Azure DevOps<\/code> :<\/p>\n<pre><code class=\"language-yml\">\r\n    - task: Bash@3\r\n      displayName: Build MacCatalyst App\r\n      inputs:\r\n        targetType: 'inline'\r\n        script: |\r\n          cd 6.0\/Apps\/WeatherTwentyOne\/src\r\n          dotnet publish -f net6.0-maccatalyst -c Release -p:BuildIpa=True -o .\/artifacts\r\n<\/code><\/pre>\n<p>To make it easier for <code>dotnet publish<\/code>, the first line navigates to the folder where the <code>WeatherTwentyOne.sln<\/code> exists. In a simpler repository structure, you would not require this first line.<\/p>\n<p>Let&#8217;s look at the <code>dotnet publish<\/code> command:<\/p>\n<p><strong><code>dotnet publish -f &lt;target_framework&gt; -c Release -p:BuildIpa=True -o &lt;path_to_output_folder&gt;<\/code><\/strong>  <\/p>\n<table>\n<thead>\n<tr>\n<th><\/th>\n<th><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>&lt;target_framework&gt;<\/code><\/td>\n<td>is set to <code>net6.0-maccatalyst<\/code> or <code>net6.0-ios<\/code> based on what you build<\/td>\n<\/tr>\n<tr>\n<td><code>-o &lt;folder_path&gt;<\/code><\/td>\n<td>allows you to redirect the publish folder from  default <em>bin\/..\/..<\/em> , instead to the folder path you specify. This is really useful for DevOps pipelines so it is easier to find the artifacts to publish.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Last task is to publish artifacts to the GitHub Pipeline,which uses the GitHub Action <a href=\"https:\/\/github.com\/marketplace\/actions\/upload-a-build-artifact\">Upload a Build Artifact<\/a>.<\/p>\n<p>In Azure DevOps, this is a two step process, fist the <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/utility\/copy-files?view=azure-devops&amp;tabs=yaml\">Copy Files Task<\/a> copies the files to the <code>$(Build.ArtifactStagingDirectory)<\/code> and then the <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/utility\/publish-build-artifacts?view=azure-devops\">Publish Build Artifacts<\/a> task publishes the artifact.<\/p>\n<p>There is one extra step for <code>iOS<\/code>, where we install the Signing Certificate and Provisioning Profile.<\/p>\n<p>This <a href=\"https:\/\/docs.github.com\/actions\/deployment\/deploying-xcode-applications\/installing-an-apple-certificate-on-macos-runners-for-xcode-development\">GitHub Documentation<\/a> explains how to install these files as part of the pipeline for <code>GitHub Actions<\/code>. Following the instructions, this is the task:<\/p>\n<pre><code class=\"language-yml\">\r\n- name: Install the Apple certificate and provisioning profile\r\n        env:\r\n          BUILD_CERTIFICATE_BASE64: ${{ secrets.BUILD_CERTIFICATE_BASE64 }}\r\n          P12_PASSWORD: ${{ secrets.P12_PASSWORD }}\r\n          BUILD_PROVISION_PROFILE_BASE64: ${{ secrets.BUILD_PROVISION_PROFILE_BASE64 }}\r\n          KEYCHAIN_PASSWORD: ${{ secrets.KEYCHAIN_PASSWORD }}\r\n        run: |\r\n          # create variables\r\n          CERTIFICATE_PATH=$RUNNER_TEMP\/build_certificate.p12\r\n          PP_PATH=$RUNNER_TEMP\/build_pp.mobileprovision\r\n          KEYCHAIN_PATH=$RUNNER_TEMP\/app-signing.keychain-db\r\n\r\n          # import certificate and provisioning profile from secrets\r\n          echo -n \"$BUILD_CERTIFICATE_BASE64\" | base64 --decode --output $CERTIFICATE_PATH\r\n          echo -n \"$BUILD_PROVISION_PROFILE_BASE64\" | base64 --decode --output $PP_PATH\r\n\r\n          # create temporary keychain\r\n          security create-keychain -p \"$KEYCHAIN_PASSWORD\" $KEYCHAIN_PATH\r\n          security set-keychain-settings -lut 21600 $KEYCHAIN_PATH\r\n          security unlock-keychain -p \"$KEYCHAIN_PASSWORD\" $KEYCHAIN_PATH\r\n\r\n          # import certificate to keychain\r\n          security import $CERTIFICATE_PATH -P \"$P12_PASSWORD\" -A -t cert -f pkcs12 -k $KEYCHAIN_PATH\r\n          security list-keychain -d user -s $KEYCHAIN_PATH\r\n\r\n          # apply provisioning profile\r\n          mkdir -p ~\/Library\/MobileDevice\/Provisioning Profiles\r\n          cp $PP_PATH ~\/Library\/MobileDevice\/Provisioning Profiles\r\n<\/code><\/pre>\n<p>On <code>Azure DevOps<\/code>, <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/apps\/mobile\/app-signing?view=azure-devops&amp;tabs=apple-install-during-build#sign-your-apple-ios-macos-tvos-or-watchos-app\">Azure DevOps Sign your Apple App<\/a> guides you through the process of adding the Certificate and Provisioning Profile file to <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/library\/secure-files?view=azure-devops\">Secure Files Library<\/a>. Once uploaded there, the <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/utility\/install-apple-certificate?view=azure-devops\">Install Apple Certificate task<\/a> and <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/utility\/install-apple-provisioning-profile?view=azure-devops\">Install Apple Provisioning Profile task<\/a> will install it as part of your pipeline task. The is what the pipeline would look like :<\/p>\n<pre><code class=\"language-yml\">\r\n - task: InstallAppleCertificate@2\r\n      inputs:\r\n        certSecureFile: 'DevelopmentCert.p12'\r\n        certPwd: '$(iOSCertPassword)'\r\n        keychain: 'temp'\r\n\r\n    - task: InstallAppleProvisioningProfile@1\r\n      inputs:\r\n        provisioningProfileLocation: 'secureFiles'\r\n        provProfileSecureFile: 'Development.mobileprovision'\r\n<\/code><\/pre>\n<h3>Windows Build Agent Pipeline<\/h3>\n<p>The build\/publish task is explained in the .NET MAUI documentation:<\/p>\n<ul>\n<li><a href=\"https:\/\/docs.microsoft.com\/dotnet\/maui\/windows\/deployment\/overview\">Publish Windows App<\/a><\/li>\n<li><a href=\"https:\/\/docs.microsoft.com\/dotnet\/maui\/android\/deployment\/overview\">Publish Android App<\/a><\/li>\n<\/ul>\n<p>For example the Android Publish task in <code>GitHub Actions<\/code> :<\/p>\n<pre><code class=\"language-yml\">\r\n- name : Build Android App\r\n          shell: bash\r\n          run: |\r\n            cd 6.0\/Apps\/WeatherTwentyOne\/src\r\n            dotnet publish -f:net6.0-android -c:Release\r\n<\/code><\/pre>\n<p>and the same task in <code>Azure DevOps<\/code> :<\/p>\n<pre><code class=\"language-yml\">\r\n    - task: Bash@3\r\n      displayName: Build Android App\r\n      inputs:\r\n        targetType: 'inline'\r\n        script: |\r\n          cd 6.0\/Apps\/WeatherTwentyOne\/src\r\n          dotnet publish -f net6.0-android -c Release\r\n<\/code><\/pre>\n<p>The first step navigates to the folder with the <code>WeatherTwentyOne.sln<\/code> and run the <code>dotnet publish<\/code> task. Let&#8217;s look at the <code>dotnet publish<\/code> command:<\/p>\n<table>\n<thead>\n<tr>\n<th><strong><code>dotnet publish -f &lt;target_framework&gt; -c Release -p:BuildIpa=True -o .\/artifacts<\/code><\/strong><\/th>\n<th><\/th>\n<th><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>&lt;target_framework&gt;<\/code><\/td>\n<td>is set to <code>net6.0-android<\/code> or <code>net6.0-windows10.0.19041.0<\/code> based on what you build<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For <code>Github Actions<\/code>, Publish artifact step remains the same, the GitHub Action <a href=\"https:\/\/github.com\/marketplace\/actions\/upload-a-build-artifact\">Upload a Build Artifact<\/a> works on both <code>Mac<\/code> and <code>Windows<\/code> agents.<\/p>\n<p>For <code>Azure Devops<\/code>,  <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/utility\/copy-files?view=azure-devops&amp;tabs=yaml\">Copy Files Task<\/a> and the <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/utility\/publish-build-artifacts?view=azure-devops\">Publish Build Artifacts<\/a> task works both on <code>Mac<\/code> and <code>Windows<\/code> agents.<\/p>\n<p>For <code>Windows<\/code>, there are two additional tasks. The first is to store and decode the Signing Certificate file.<\/p>\n<p>In <code>GitHub Actions<\/code>, the process for it is as following:<\/p>\n<ol>\n<li>The Signing Certificate file created needs to be encoded into Base64. This can be done using <code>certutil<\/code> on <code>Windows<\/code>, follow the <a href=\"https:\/\/docs.microsoft.com\/windows-server\/administration\/windows-commands\/certutil\">documentation<\/a>. On <code>Mac<\/code>, you can run <code>base64 -i &lt;cert_file&gt;.pfx | pbcopy<\/code>.<\/li>\n<li>The Base64 encoded string needs to be stored in GitHub Actions Secrets by following the <a href=\"https:\/\/docs.github.com\/actions\/security-guides\/encrypted-secrets#creating-encrypted-secrets-for-a-repository\">GitHub Actions Encrypted Secrets Documentation<\/a>.<\/li>\n<li>Decode the secret in the Pipeline task:<\/li>\n<\/ol>\n<pre><code class=\"language-yml\">\r\n- name: Create signing pfx file from secrets\r\n        shell: pwsh\r\n        id: secret-file\r\n        env:\r\n          SIGN_CERT: ${{ secrets.WIN_SIGN_CERT }}\r\n        run: |\r\n          $secretFile = \"WinSignCert.pfx\"; \r\n          $encodedBytes = [System.Convert]::FromBase64String($env:SIGN_CERT); \r\n          Set-Content $secretFile -Value $encodedBytes -AsByteStream;\r\n          Write-Output \"::set-output name=SECRET_FILE::$secretFile\";\r\n<\/code><\/pre>\n<p>In <code>Azure DevOps<\/code>, follow the <a href=\"https:\/\/docs.microsoft.com\/windows\/msix\/desktop\/cicd-overview\">CI\/CD Pipeline Overview<\/a> guide and upload the file to <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/library\/secure-files?view=azure-devops\">Secure Files Library<\/a>. Then download and install the file using the <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/utility\/download-secure-file?view=azure-devops\">Download Secure File task<\/a>:<\/p>\n<pre><code class=\"language-yml\">\r\n    - task: DownloadSecureFile@1\r\n      inputs:\r\n        secureFile: 'DevelopmentCert.pfx'\r\n<\/code><\/pre>\n<p>The second task is to use this Certificate file to sign the MSIX generated from <code>dotnet publish<\/code>. Following this <a href=\"https:\/\/docs.microsoft.com\/windows\/msix\/desktop\/azure-dev-ops\">Azure DevOps Guide<\/a>, we get the following task in <code>GitHub Actions<\/code>:<\/p>\n<pre><code class=\"language-yml\">\r\n- name: Sign Windows App\r\n        shell: pwsh\r\n        env:\r\n          CERT_PASSWORD: ${{ secrets.WIN_CERT_PASSWORD }}\r\n        run: |\r\n          '\"C:Program Files (x86)Windows Kits10App Certification KitSignTool\" sign \/a \/fd SHA256 \/f WinSignCert.pfx \/p ($env:CERT_PASSWORD) 6.0AppsWeatherTwentyOnesrcWeatherTwentyOnebinReleasenet6.0-windows10.0.19041.0win10-x64AppPackagesWeatherTwentyOne_1.0.0.0_TestWeatherTwentyOne_1.0.0.0_x64.msix'\r\n<\/code><\/pre>\n<p>and the same task in <code>Azure DevOps<\/code>, directly using the code snippet provided in the guide:<\/p>\n<pre><code class=\"language-yml\">\r\n    - script: '\"C:Program Files (x86)Windows Kits10App Certification KitSignTool\" sign \/fd SHA256 \/f $(Agent.TempDirectory)\/XamCATFidCert.pfx \/p $(WindowsCertSecret) $(Build.ArtifactStagingDirectory)6.0AppsWeatherTwentyOnesrcWeatherTwentyOnebinReleasenet6.0-windows10.0.19041.0win10-x64AppPackagesWeatherTwentyOne_1.0.0.0_TestWeatherTwentyOne_1.0.0.0_x64.msix'\r\n      displayName: 'Sign MSIX Package'\r\n<\/code><\/pre>\n<p>In <code>GitHub Actions<\/code> for <code>Android Signing<\/code>, the sample pipelines contains the tasks, uncomment and follow the links as needed. Similar to <code>Windows<\/code>, first encode in Base64 and decode the Keystore file. The next task is to sign the generated <code>apk<\/code> file using <code>jarsigner<\/code>.<\/p>\n<p>In <code>Azure DevOps<\/code> for <code>Android Signing<\/code>, this guide shows step by step how to <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/apps\/mobile\/app-signing?view=azure-devops&amp;tabs=apple-install-during-build#sign-your-android-app\">Sign your Android App<\/a>. It shows how to upload the signing files securely and then how to configure the <code>Azure DevOps<\/code> task for <a href=\"https:\/\/docs.microsoft.com\/azure\/devops\/pipelines\/tasks\/build\/android-signing?view=azure-devops\">Android Signing<\/a>.<\/p>\n<h2>Summary<\/h2>\n<p>I hope this helps you get started with setting up DevOps for .NET MAUI apps using <code>GitHub Actions<\/code> and <code>Azure DevOps<\/code>. The sample <code>yaml<\/code> files:<\/p>\n<ul>\n<li>\n<p>GitHub Actions Samples<\/p>\n<ul>\n<li>MacOS Hosted Agent : <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/GitHubActions\/macos-build.yml\">macos-build.yml<\/a><\/li>\n<li>Windows Hosted Agent: <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/GitHubActions\/windowsCI.yml\">windowsCI.yml<\/a><\/li>\n<\/ul>\n<\/li>\n<li>\n<p>Azure DevOps Samples<\/p>\n<ul>\n<li>MacOS Hosted Agent : <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/AzureDevOps\/azdo_mac.yml\">azdo_mac.yml<\/a><\/li>\n<li>Windows Hosted Agent: <a href=\"https:\/\/github.com\/dotnet\/maui-samples\/blob\/main\/6.0\/Apps\/WeatherTwentyOne\/devops\/AzureDevOps\/azdo_windows.yml\">azdo_windows.yml<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Check out the more samples at <a href=\"https:\/\/github.com\/dotnet\/maui-samples\">dotnet\/maui-samples<\/a>. Please try out .NET MAUI, file issues, or learn more at <a href=\"https:\/\/dot.net\/maui\">dot.net\/maui<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Want to add DevOps to your .NET MAUI project? This post shows how to implement a starter pipeline using GitHub Actions and Azure DevOps.<\/p>\n","protected":false},"author":1969,"featured_media":40588,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[685,7233,327,7589],"tags":[7650,7649,7606,7605,7608],"class_list":["post-40587","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dotnet","category-maui","category-azure","category-github-actions","tag-azure-devops","tag-ci-cd","tag-continuous-integration","tag-devops","tag-github-actions"],"acf":[],"blog_post_summary":"<p>Want to add DevOps to your .NET MAUI project? This post shows how to implement a starter pipeline using GitHub Actions and Azure DevOps.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/40587","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/1969"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=40587"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/40587\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/40588"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=40587"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=40587"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=40587"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}