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

[Feedback] Can not update to .NETCore 1.1.0 after upgrading to Microsoft.NETCore.UniversalWindowsPlatform v5.3.0 #20266

Closed
rrelyea opened this issue Feb 17, 2017 · 6 comments
Labels
area-Meta question Answer questions and provide assistance, not an issue with source code or documentation.
Milestone

Comments

@rrelyea
Copy link
Contributor

rrelyea commented Feb 17, 2017

Internal bug 385268 & vsfeedback issue 806440
Create UWP project with VS2015 and upgrade UWP package to v5.2.2 Open project in VS2017 RC3 - RC4. Open Manage NuGet packages for solution and check available updates. Microsoft.NETCore.Runtime.CoreCLR v1.1.0 is listed as package available for update. Trying to update fails with error message:
GET https://api.nuget.org/v3/registration1-gz/microsoft.netcore.jit/index.json
OK https://api.nuget.org/v3/registration1-gz/microsoft.netcore.jit/index.json 661ms
Restoring packages for E:\src\tools{Project path and Name}\project.json...
GET https://api.nuget.org/v3-flatcontainer/runtime.win8-arm.microsoft.netcore.jit/index.json
NotFound https://api.nuget.org/v3-flatcontainer/runtime.win8-arm.microsoft.netcore.jit/index.json 533ms
Unable to resolve 'runtime.win8-arm.Microsoft.NETCore.Jit (>= 1.1.0)' for 'UAP,Version=v10.0 (win10-arm)'.
Unable to resolve 'runtime.win8-arm.Microsoft.NETCore.Jit (>= 1.1.0)' for 'UAP,Version=v10.0 (win10-arm-aot)'.
it seems that win7-x86 and win7-x64 versions are available on nuget while arm version of assembly is available only as a preview package

Copied from: NuGet/Home#4643

@rrelyea
Copy link
Contributor Author

rrelyea commented Feb 17, 2017

@jainaashish (nuget team) found: runtime.win8-arm.microsoft.netcore.jit package isn't available on NuGet.org which is why this update failed. DotNet team needs to look into this and publish this package.

@ericstj

@karelz
Copy link
Member

karelz commented Feb 18, 2017

Does not look like CoreFX issue, rather like a problem in tooling - @davkean @eerhardt can you please advise where to route it?
cc: @danmosemsft

@davkean
Copy link
Member

davkean commented Feb 20, 2017

@karelz CoreFX own these packages and the uploading of them.

@tarekgh
Copy link
Member

tarekgh commented Feb 21, 2017

@ericstj do you know what is the issue here?

@ericstj
Copy link
Member

ericstj commented Feb 21, 2017

This is actually a coreclr issue and should be moved to that repo. @gkhanna79.

The same issue was hit in 1.0.x that package was hardcoded to use the 1.0.2 packages built out of TFS.

I suspect that the same fix hasn't been made to 1.1.0 and the ARM build of JIT packages is still missing.

In the meantime, don't upgrade CoreCLR or JIT packages. Just keep the ones brought in by the UWP meta-package.

@tarekgh
Copy link
Member

tarekgh commented Feb 21, 2017

Issue moved to dotnet/coreclr dotnet/corefx#9694 via ZenHub

@tarekgh tarekgh closed this as completed Feb 21, 2017
@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.0.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Meta question Answer questions and provide assistance, not an issue with source code or documentation.
Projects
None yet
Development

No branches or pull requests

6 participants