Stride Launcher Directs Users to Runtime Install When SDK is Missing
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release
Version:
Stride Launcher 5.0.6
Stride 4.1.0.1838
Describe the bug
In a development environment without the .NET 6.0 SDK installed, the user is prompted to install the SDK when launching Stride 4.1.x. The prompt will direct them to the download page for the .NET 6.0 Desktop Runtime and not the SDK.
Subsequent launches will no longer warn that the SDK isn't installed, the user will only be notified when attempt to build their project.
To Reproduce
Steps to reproduce the behavior:
- Launch Stride Launcher 5.0.6 on a PC without the .NET 6.0 SDK installed
- When the Launcher prompts about a required .NET install or update, press "Yes"
- Your default browser should launch and direct you to the download page for the Runtime
Expected behavior
The Launcher prompt should direct users to the latest version of the .NET 6.0 SDK
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Reproduce the issue with Stride Launcher 5.0.6 on a system without the .NET 6.0 SDK, then locate the launcher code that checks the required installation and constructs the download link. Done means the prompt opens the .NET 6.0 SDK download page and the warning behavior remains correct on later launches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100