Skip to content

Azure Endpoint for .NET 8 WindowsDesktop Runtime Points to Outdated Version #395

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

Closed
Sewer56 opened this issue Sep 17, 2023 · 6 comments
Closed

Comments

@Sewer56
Copy link

Sewer56 commented Sep 17, 2023

I'm not sure of the exact place to report it; so I apologize if this is not the right place.

I'll keep it simple.

The Azure endpoint used by the dotnet-install scripts is pointing to the wrong version of the runtime for the WindowsDesktop FrameworkName. Which means that the install script will fetch an outdated version of this runtime if requested. For the same reason, various libraries such as my own NetCoreInstallChecker are affected.

Link: https://dotnetcli.azureedge.net/dotnet/WindowsDesktop/8.0/latest.version

The URLs for main runtime and ASP.NET are up to date as expected, it's just WindowsDesktop.

This should be at RC1 instead of Preview 7, however 4 days have elapsed since RC1 release; and this endpoint has not yet unfortunately been updated; so I'm formally opening a ticket for this.

@Sewer56 Sewer56 changed the title Azure Endpoint for .NET 8 WindowsDesktop SDK Points to Outdated Version Azure Endpoint for .NET 8 WindowsDesktop Runtime Points to Outdated Version Sep 17, 2023
@Suchiman
Copy link

It's not just WindowsDesktop / 8.0, it also affects 7.0, e.g. https://dotnetcli.azureedge.net/dotnet/Sdk/STS/latest.version is still at 7.0.400 while it should be 7.0.401

@YuliiaKovalova
Copy link
Member

Hi @Sewer56,

I am looking at this issue.

@YuliiaKovalova YuliiaKovalova self-assigned this Sep 18, 2023
@YuliiaKovalova
Copy link
Member

YuliiaKovalova commented Sep 18, 2023

Hi @Sewer56 , @Suchiman ,

Could you check if the issue is still relevant to you?

@Sewer56
Copy link
Author

Sewer56 commented Sep 18, 2023

Hi @Sewer56 , @Suchiman ,

Could you check if the issue is still relevant to you?

Appears to be updated on my end 👍

@Suchiman
Copy link

Yep, works fine now, can be closed 👍

@YuliiaKovalova
Copy link
Member

Thank you for your cooperation with us :)

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

3 participants