Skip to content
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

[.NET 10] missing Mono and Emscripten manifests for downlevel .NET 9 targeting #110318

Open
jonathanpeppers opened this issue Dec 2, 2024 · 4 comments

Comments

@jonathanpeppers
Copy link
Member

Description

Looking here:

We are missing packs like:

  • Microsoft.NET.Workload.Mono.ToolChain.net9.Manifest-10.0.100-alpha.1
  • Microsoft.NET.Workload.Emscripten.net9.Manifest-10.0.100-alpha.1

Note that we have the Current, net6, net7, and net8 manifest packs here.

Missing net9 manifests prevents us from building net9.0-* projects with a .NET 10 SDK, at:

This is blocking us from getting a build of .NET MAUI on .NET 10.

Reproduction Steps

dotnet workload install android --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet10/nuget/v3/index.json with a .NET 10 SDK.

Expected behavior

These manifest packs exist on the dotnet10 feed:

  • Microsoft.NET.Workload.Mono.ToolChain.net9.Manifest-10.0.100-alpha.1
  • Microsoft.NET.Workload.Emscripten.net9.Manifest-10.0.100-alpha.1

Actual behavior

These manifest packs do not exist on the dotnet10 feed:

  • Microsoft.NET.Workload.Mono.ToolChain.net9.Manifest-10.0.100-alpha.1
  • Microsoft.NET.Workload.Emscripten.net9.Manifest-10.0.100-alpha.1

Regression?

Yes, .NET 10 should support building net9.0-* projects.

Known Workarounds

None

Configuration

  • .NET SDK 10.0.100-alpha.1.24573.1
  • .NET runtime 10.0.0-alpha.1.24570.9

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 2, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 2, 2024
Copy link
Contributor

Tagging subscribers to this area: @akoeplinger, @matouskozak
See info in area-owners.md if you want to be subscribed.

@jonathanpeppers
Copy link
Member Author

/cc @steveisok @lewing

@lewing
Copy link
Member

lewing commented Dec 2, 2024

yup, we're waiting for some sdk changes before adding it

@teo-tsirpanis teo-tsirpanis removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 3, 2024
@steveisok steveisok added this to the 10.0.0 milestone Dec 9, 2024
@steveisok steveisok removed the untriaged New issue has not been triaged by the area owner label Dec 9, 2024
@marcpopMSFT
Copy link
Member

yup, we're waiting for some sdk changes before adding it

@lewing what changes are you still waiting on for this? I thought that all net10 changes I was tracking were in other than unwinding some test disablements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants