Has anyone successfully built xamarin ios project on AzureDevOps using multi targeting libraries with TargetFrameworks netstandard2.1 & net8.0

[nikamvd]

Apple platform

iOS

Framework version

Other

Affected platform version

XamariniOS@2 task on vmImage: macos-13 on azure devops

Description

We migrated our Xamarin.Forms project to .NET MAUI (.net 8.0). We are still supporting our Xamarin.Forms project. The common organization level libraries now target multiple frameworks netstandard2.1;net8.0. .NET MAUI pipelines are working good. xamarin android pipeline is also working; however xamarin ios pipeline build task fails with error NETSDK1005: Assets file 'project.assets.json' doesn't have a target for '.NETFramework,Version=v8.0'. Ensure that restore has run and that you have included 'net80' in the TargetFrameworks for your project.

Has anyone successfully built xamarin ios project on AzureDevOps using multi targeting libraries?

Steps to Reproduce

We migrated our Xamarin.Forms project to .NET MAUI (.net 8.0). We are still supporting our Xamarin.Forms project. The common organization level libraries now target multiple frameworks netstandard2.1;net8.0. .NET MAUI pipelines are working good. xamarin android pipeline is also working; however xamarin ios pipeline build task fails with error NETSDK1005: Assets file 'project.assets.json' doesn't have a target for '.NETFramework,Version=v8.0'. Ensure that restore has run and that you have included 'net80' in the TargetFrameworks for your project.

Has anyone successfully built xamarin ios project on AzureDevOps using multi targeting libraries?

Did you find any workaround?

No

Build logs

No response

[rolfbjarne]

This repository is for the .NET for iOS SDK - formerly known as Xamarin.iOS (but Xamarin.iOS is now out of support).

Because Xamarin.iOS is out of support, we won't investigate/support any issues related to it, which means that the broader developer community would be the best and quickest place for additional troubleshooting help on this issue.

Posting a question on Stack Overflow, the .NET on Q&A Forum or asking on Discord would be the best next step.