> Microsoft will only publish packages for distros where .NET packages are not included in the distro archive.

[amatahoo]

Microsoft will only publish packages for distros where .NET packages are not included in the distro archive.

This decision has some implications. Currently not all workloads are supported for distro build SDK versions. This is especially true for MAUI workloads, the progress on that is tracked in dotnet/source-build#3242

As a result it is impossible to build MAUI application on any distro where only the distro build SDK versions are supported. The only workaround is to install .NET manually using the installer script or by downloading manually. It will also occur on distros where Microsoft still publishes the SDK using the Microsoft feed if you choose to use the recommended and most convenient installation method of using distro provided SDKs. A full description of this issue can be found in dotnet/sdk#41123

This behavior is not documented anywhere. Furthermore, you will be presented with an error that is completely intransparent about this limitation

Workload ID maui-android is not recognized.

I see two options to mitigate this issue:

• Publish Microsoft packages for distros where .NET packages are included (in short: abandon the policy described here)
• Speed up the work in Pull in MAUI repo(s) in order to source-build MAUI manifest nupkgs source-build#3242

The issue has no progress for almost a year now.

There are other users having the same problem:

• Workload ID maui-android is not recognized sdk#38171
• Not able to install MAUI on ArchLinux system sdk#40576
• Default xplat project cannot be built when .net8.0 is installed on linux (NETSDK1139: target platform 'android' is not recognized). AvaloniaUI/Avalonia#14897

According to dotnet/source-build#3242 (comment) this does also affect android and macos workloads, apart from the MAUI workloads.

Originally posted by @klemmchr in #9258 (comment)