microsoft / microsoft/vscode-dotnettools
Surface actionable restore failures in C# Workspace Requirements
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 issue
When automatic restore fails, it can be difficult to discover why project loading is blocked or how to resolve it.
For example, a package source may require an interactive restore. Restore fails, but C# Workspace Requirements does not clearly identify the failure or provide a remediation path.
C# Workspace Requirements should:
- Show restore as an unmet workspace requirement.
- Present the underlying error in clear, user-friendly language.
- Identify when an interactive restore is required.
- Provide a Run interactive restore action.
- Link to detailed restore output when further investigation is needed.
- Re-evaluate workspace readiness after a successful restore.
Collect logs
Not needed; this issue concerns how known restore failures are presented and remediated.
Steps to reproduce
- Open a workspace that references a package source requiring interactive authentication.
- Allow C# Dev Kit to run automatic restore.
- Observe that restore fails.
- Open C# Workspace Requirements.
- Observe that the restore failure and remediation are not clearly surfaced.
Expected behavior
C# Workspace Requirements should show the restore failure as a blocker, explain that an interactive restore is required, and provide a Run interactive restore action.
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
Begin with C# Workspace Requirements and the automatic restore flow described in the reproduction steps. Trace how failed restore results and detailed restore output are currently surfaced, then follow the interactive restore path. Done means the view identifies restore as a blocker, explains interactive authentication, offers Run interactive restore, links detailed output, and refreshes after success.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100