-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Feature request
Please include the following information:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. E.g. I'm always frustrated when [...]
No.
Describe the solution you'd like.
A clear and concise description of what you want to happen.
The document points to an incorrect download link for Visual Studio 2022. The link https://visualstudio.microsoft.com/vs/ mentioned at https://www.graalvm.org/latest/reference-manual/native-image/ will lead users to download Visual Studio 2026, not Visual Studio 2022.
The download link for Visual Studio 2022 appears to have been hidden by Microsoft.
Describe who do you think will benefit the most.
GraalVM users, GraalVM contributors, developers of libraries and frameworks which depend on GraalVM, or somebody else?
GraalVM users.
Describe alternatives you've considered.
A clear and concise description of any alternative solutions or features you've considered.
Perhaps we could directly ask users to use winget in PowerShell 7 to install Visual Studio 2022. This directly avoids downloading the wrong Visual Studio 2026.
winget install --id Microsoft.VisualStudio.2022.Community --source wingetAdditional context.
Add any other context about the feature request here.
For example, link to the relevant projects, documentation, standards.
This relates to https://devblogs.microsoft.com/visualstudio/visual-studio-2026-is-here-faster-smarter-and-a-hit-with-early-adopters/ .
Express whether you'd like to help contributing this feature
If you'd like to contribute, please read the contribution guide.
I'm not sure if it's necessary to raise the minimum MSVC version supported by GraalVM CE to Visual Studio 2026, and I'm afraid I can't be of much help.