trasloco

XamariniOS@1 is retired: migrate off its platform or external tool

The short answer

Retirement date
Removal date
. Pipelines that still use it fail after removal.
Replacement
Closest task: DotNetCoreCLI@2 (after the migration described below).
Kind of migration
retired platform or external tool: no drop-in replacement
Automatic rewrite
No. This task needs a manual migration. trasloco modernize --check still finds the step.
Recommended action
Migrate the project to SDK-style .NET or .NET MAUI before using DotNetCoreCLI@2.

Official sources

Last verified:

Why does my pipeline show a retirement error for XamariniOS@1?

On , Azure Pipelines shows a retirement error for XamariniOS@1, but the run does not fail. On , pipelines that still use XamariniOS@1 fail.

Find it in your pipelines

With trasloco:

trasloco modernize --check

Install trasloco from the latest release.

With plain grep, nothing to install:

grep -rniwF 'XamariniOS@1' --include='*.yml' --include='*.yaml' .

How to migrate

Migrate the project to SDK-style .NET or .NET MAUI before using DotNetCoreCLI@2.

The task definition of the replacement is linked under official sources above.

XamariniOS@1 retirement FAQ

Is XamariniOS@1 deprecated?

Yes. XamariniOS@1 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.

When does XamariniOS@1 stop working?

XamariniOS@1 is removed on 2027-03-15. Pipelines that still use it fail after removal.

What should I use instead of XamariniOS@1?

DotNetCoreCLI@2 is the closest task, after the platform or tool migration described on this page.