Portable RID PublishAOT doesn't work from source-build VMR .NET 9 Preview 5

[omajid]

Describe the bug

Trying to publish a hello-world console application with a source-build VMR targeting a portable RID doesn't work. Neither does using --use-current-runtime.

To Reproduce

[omajid@828429dd39b9 ~]$ dotnet publish -r linux-x64 /p:PublishAot=true
    /home/omajid/omajid.csproj : error NU1101: Unable to find package runtime.fedora.40-x64.Microsoft.DotNet.ILCompiler. No packages exist with this id in source(s): nuget.org

Restore failed with 1 error(s) in 12.6s
[omajid@828429dd39b9 ~]$ dotnet publish --use-current-runtime /p:PublishAot=true
    /home/omajid/omajid.csproj : error NU1101: Unable to find package runtime.fedora.40-x64.Microsoft.DotNet.ILCompiler. No packages exist with this id in source(s): nuget.org

Restore failed with 1 error(s) in 0.7s

Further technical details

• Include the output of dotnet --info

[omajid@828429dd39b9 ~]$ dotnet --info
.NET SDK:
 Version:           9.0.100-preview.5.24307.1
 Commit:            35b2c21ea6
 Workload version:  9.0.100-manifests.9b4ca231
 MSBuild version:   17.11.0-preview-24279-02+b963c24ef

Runtime Environment:
 OS Name:     fedora
 OS Version:  40
 OS Platform: Linux
 RID:         fedora.40-x64
 Base Path:   /usr/lib64/dotnet/sdk/9.0.100-preview.5.24307.1/

.NET workloads installed:
Configured to use loose manifests when installing new manifests.
There are no installed workloads to display.

Host:
  Version:      9.0.0-preview.5.24306.7
  Architecture: x64
  Commit:       a5cc707d97

.NET SDKs installed:
  9.0.100-preview.5.24307.1 [/usr/lib64/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 9.0.0-preview.5.24306.11 [/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 9.0.0-preview.5.24306.7 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  DOTNET_ROOT       [/usr/lib64/dotnet]

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

cc @tmds

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[am11]

It probably needs #41198 (latest preview 6 build)

[omajid]

I was expecting that would fix matching/non-portable RID builds. Will that also fix portable RID builds?

[am11]

dotnet-publish will use the bundled ILCompiler package with that change (and skip looking for it in nuget feeds).

[omajid]

Even if the user wants to target portable RIDs?

[tmds]

No, then it should download the linux-x64 ILCompiler.
I'll take a closer look after the weekend.

[am11]

dotnet publish -r linux-x64 should work. --use-current-runtime or --ucr will get us non-portable RID on non-portable build.

[tmds]

--use-current-runtime or --ucr will get us non-portable RID on non-portable build.

No, it will use the portable rid to enable a consistent user-experience between portable and non-portable builds.

The issue with preview5 is that it knows about the non-portable ILCompiler and ProcessFrameworkReferences prefers that for the host over the portable one. We need to fix this. This is the desired behavior: dotnet/source-build#1215 (comment).

[am11]

No, it will use the portable rid to enable a consistent user-experience between portable and non-portable builds.

Ah, I forgot that --ucr refers to NETCoreSdkPortableRuntimeIdentifier.