-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mono: The logic to find the RuntimeComponentManifest.json file is incorrect #56299
Comments
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. |
Tagging subscribers to this area: @directhex Issue DetailsDescriptionThe logic to find the RuntimeComponentManifest.json here: runtime/src/mono/nuget/Microsoft.NET.Runtime.MonoTargets.Sdk/Sdk/RuntimeComponentManifest.targets Line 6 in 893739f
does not take into account that See binlog: Here's the
The end result is that the last one is picked, and the code fails because it expects to find RuntimeComponentManifest.json in
|
When trying to process what runtime components are available, we were assuming %(ResolvedRuntimePack.PackageDirectory) would give us the correct Microsoft.NETCore.App runtime pack. Unfortunately, the ordering was likely altered when we started setting <KnownRuntimePack> items in the Mono workload. Since relying on position of the items isn't reliable, we will instead use %(ResolvedFrameworkReference) to tell us which runtime pack is active and where it's located. Fixes dotnet#56299
Description
The logic to find the RuntimeComponentManifest.json here:
runtime/src/mono/nuget/Microsoft.NET.Runtime.MonoTargets.Sdk/Sdk/RuntimeComponentManifest.targets
Line 6 in 893739f
does not take into account that
ResolvedRuntimePack
might contain more than one runtime pack.See binlog:
msbuild.binlog.zip
Here's the
ResolvedRuntimePack
items:The end result is that the last one is picked, and the code fails because it expects to find RuntimeComponentManifest.json in
Microsoft.macOS.Runtime.osx-x64
, and notMicrosoft.NETCore.App.Runtime.Mono.osx-x64
.CC @lambdageek, @steveisok
The text was updated successfully, but these errors were encountered: