Thats right Xamarin is still kicking. Maui is technically GA but any team with a few Xamarin apps under their belt would tell you that migration is not easy and Xamarin still has some life in it. The best thing about Xamarin at this point is that it is very stable, it has been stable for a few years and you seldom run into issues with the framework.If you do the ecosystem is very mature and theres most likely a nuget package to solve your problem.
This post will focus on running unit tests in Azure Pipelines, making sure that builds work properly with some of the caviats that we need to account for with Xamarin being incompatible with newer dotnet versions.
Xamarin projects do not work well with .NET 5 and above, the moment you increase the unit test csproj version to target
net5.0, you are in for a world of problems. Looking at popular library Xamarin.CommunityToolkit, their test project is still targetting
At this point newer dotnet versions (5+) won’t support your xamarin projects so we have to make do with dotnet core 3.1.
You might be using global.json to pin down a .NET version. If you are using a .NET 5 version, it is time to upgrade to .NET 6. .NET 5 and .NET Core 3.1 are incompatible and the dotnet cli cannot run tests correctly when using these 2 versions, this is not an issue when using .NET 6 and .NET Core 3.1.
The steps are simple:
The following YAML should work to build and run your tests:
- task: NuGetToolInstaller@1 displayName: Use latest NuGet inputs: checkLatest: true - task: UseDotNet@2 displayName: 'Install .NET SDK' inputs: version: '6.0.x' - task: UseDotNet@2 displayName: 'Install .NET 3.1 Test SDK' inputs: version: '3.1.x' - task: UseDotNet@2 displayName: 'Install .NET 2.1 Test SDK' inputs: version: '2.1.x' - task: DotNetCoreCLI@2 displayName: 'dotnet restore' inputs: command: restore projects: '**/*.csproj' - task: DotNetCoreCLI@2 displayName: 'dotnet test' inputs: command: test projects: '**/*.Test*.csproj' publishTestResults: false
I had alot of issues when targetting .NET 5, the
dotnet test step would always fail with minimal information, even in debug mode!
The azure pipeline would display the following message:
##[error]Error: The process 'C:\hostedtoolcache\windows\dotnet\dotnet.exe' failed with exit code 1 ##[warning].NET 5 has some compatibility issues with older Nuget versions(<=5.7), so if you are using an older Nuget version(and not dotnet cli) to restore, then the dotnet cli commands (e.g. dotnet build) which rely on such restored packages might fail. To mitigate such error, you can either: (1) - Use dotnet cli to restore, (2) - Use Nuget version 5.8 to restore, (3) - Use global.json using an older sdk version(<=3) to build Info: Azure Pipelines hosted agents have been updated and now contain .Net 5.x SDK/Runtime along with the older .Net Core version which are currently lts. Unless you have locked down a SDK version for your project(s), 5.x SDK might be picked up which might have breaking behavior as compared to previous versions. You can learn more about the breaking changes here: https://docs.microsoft.com/en-us/dotnet/core/tools/ and https://docs.microsoft.com/en-us/dotnet/core/compatibility/ . To learn about more such changes and troubleshoot, refer here: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshooting ##[error]Dotnet command failed with non-zero exit code on the following projects : [ 'D:\\a\\1\\s\\AcmeProject.Tests\\AcmeProject.Tests.csproj' ] Finishing: dotnet test
This error is specific to .NET 5, to fix the issue upgrade your SDK target to 6:
- task: UseDotNet@2 displayName: 'Install .NET SDK' inputs: version: '6.0.x'
Xamarin.CommunityToolkit contains a rouge reference to a windows library that affects the test runner when performing tests on visual studio for mac.
You will find that the unit test project builds but the test runner UI picks up no tests and when executing the runner, it will hang and not execute any tests. Regardless of how many tests are in your project, the tests will not get picked up:
The following issues over on their github all are caused by this rogue reference:
To fix this add the following lines to your csproj:
<PropertyGroup> <TargetFrameworks>netcoreapp3.1</TargetFrameworks> <GenerateErrorForMissingTargetingPacks>false</GenerateErrorForMissingTargetingPacks> </PropertyGroup>
You can also optionally ignore the nuget warnings generated by the same issue with XCT:
Your tests should now work in Visual Studio for Mac again! 😄