Configure CI pipeline with .NET MAUI Release candidate (for NuGets)

This content has 2 years. Some of the information in this post may be out of date or no longer work. Please, read this page keeping its age in your mind.In order to do automated builds in Azure DevOps with the .NET MAUI Release Candidate release, we need a few extra steps in the pipeline configuration. I used these steps to ensure that the NuGet packages I develop are automatically compiled and uploaded to NuGet.org. In this article I won’t go into detail about how to create a CI pipeline, I just want to show you the difference from a normal CI pipeline. I haven’t tried building and deploying applications in the cloud at the moment, but it can probably be done. Also, I don’t go into how to make the package automatically go to NuGet.org, for that I recommend an earlier article (and also how to create a CI/CD pipeline): https://www.banditoth.net/2021/11/09/azure-devops-setup-private-nuget-feed-with-ci/ Since a final version of .NET MAUI has not been released as of today, in order to build our applications in the cloud, we need to install the MAUI Workload on the Agent.If we do not do this, we may encounter the following error: Adjust your pipeline In order to install the workload on our build agent, create a new task at the very beginning in the pipeline file, which is executes a command in the command line: This will result the following task in the yaml file: The installation of the workload will take about 5 minutes….

Complete CI/CD tutorial for Xamarin Android with Google Play publish in Azure DevOps | Part 2.

This content has 4 years. Some of the information in this post may be out of date or no longer work. Please, read this page keeping its age in your mind.If you haven’t seen part 1, click here, and start build up your CI/CD pipeline now. Part 2 Contains: Configuring build with creating signed APK, and making artifacts from it Setting up branch policy to master Configure some magic Let’s go back to Pipelines. Edit your previously created pipeline by clicking the three dot on the pipelines row. CI is based on cloud machines hosted somewhere over the world. This computers called as agents. They are used to follow your instructions, defined in the yml file. The base Xamarin.Android yml is only to build your code. But we will make some additional steps in order to create a signed APK of every build. Follow up, to complete this setup. Recommended branching strategy for this is to keep a development branch, and pull request your feature branches to it, and finally pull request the development branch to the master, and keep your master is always at your production version. The figure below shows visually this method. Source: https://dzone.com/articles/feature-branching-using-feature-flags-1 Create a signed APK or bundle from every build First, set up some variables for this pipeline. You will find a Variables button on the right top of the tab. Click on it. Let’s add a new variable by clicking the “New variable” button. We will need 4 vars. Remember, that i told…

Complete CI/CD tutorial for Xamarin Android with Google Play publish in Azure DevOps | Part 1.

This content has 4 years. Some of the information in this post may be out of date or no longer work. Please, read this page keeping its age in your mind.This tutorial will drive you through setting up a great CI/CD pipeline for Xamarin Android in a fully hosted Azure DevOps enviroment. Part 1 contains: Creating an empty Xamarin.Android build pipeline Uploading keystore file to secure files Start with some code I have added some basic code to my demo repository. It is a boilerplate Xamarin Application, with no additional customized code. If you have code in your repo, make sure it builds successfully. Create your first pipeline On the left side menu, go to Pipelines/Pipelines. This menu will show up a welcome page, to create new pipeline. Click on ‘Create Pipeline’ button, or if you have already created your first pipeline, find a button to add a new one. On the next page, a wizard will guide you through the basic setup. If you have your code in Azure Repos, click the button for that. Select your repository where your Xamarin Android code lives. On the next page, you can select a template to create your pipeline yml. Let’s choose Xamarin.Android. If you want, you can rename your yml file. Pipeline files will be placed in your repository root by default. YML file extension stands for YAML files. Review your newly created file, how it looks like. Luckily, you do not have to write yaml too much, but good…