microsoft / microsoft/vscode-dotnettools
[SUGGESTION] Improve Installation Process to Require Explicit User Consent for SDK Downloads
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Describe the feature you'd like
I'd like to see an enhanced installation process for the C# Dev Kit extension that mandates explicit user consent before proceeding with any installations or modifications to the environment and system configurations. The current process appears to autonomously initiate installations without prior user approval, closely mirroring the behavior of unauthorized software. This not only disrupts the work environment but also raises concerns regarding user autonomy and system integrity. An improved process should include clear notifications detailing the intended changes and require an explicit user action to proceed, thereby respecting user preferences and ensuring transparency.
Alternatives considered
I have considered the following alternatives to address my concerns:
- Manual Installation Option: Allowing users to manually download and install updates or new installations, providing them with control over when and how changes are applied.
- Opt-In Updates: Implementing an opt-in mechanism for updates or installations, where users are prompted to approve any changes before they are executed.
- Detailed Pre-Installation Summary: Presenting a detailed summary of the proposed changes and effects on the current environment, giving users a comprehensive understanding of the impact before they consent to the installation.
These alternatives aim to enhance user control and transparency, ensuring that the extension's installations and updates do not compromise the integrity of the user's environment without their informed consent.
Environment Information
- OS: [e.g. Windows10]
- VS Code: [e.g. v1.86.2]
- Extension Version: [e.g. v1.3.10]
Contributor guide
No contributing guide indexed for this repository
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 files, tests, or entry points are named. Start by tracing the C# Dev Kit extension's installation and update flow, then review how it currently handles SDK downloads and environment changes. Done means the proposed consent model is defined, including notifications, explicit approval, and the manual or opt-in alternatives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100